RP3DAA64.dll file report

MD5 3498f4b440fc63ab55eeeef90e5c25d4
Latest seen 2021-01-04 06:41:31 (5 years ago)
First seen 2017-05-22 09:06:34 (8 years ago)
Size 314 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 09:06:34 (8 years ago); latest analysis 2021-01-04 06:41:31 (5 years ago).

Publisher context

Company metadata: Dolby Laboratories, Inc.. Product metadata: Dolby PCEE3 Control Panel.

Digital signature

Signed by Dolby Laboratories, Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

RP3DAA64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Dolby PCEE3 Control Panel. The reported company name is Dolby Laboratories, Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-04 06:41:31 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Dolby PCEE3 Control Panel
Company Name: Dolby Laboratories, Inc.
MD5: 3498f4b440fc63ab55eeeef90e5c25d4
Size: 314 KB
First Published: 2017-05-22 09:06:34 (8 years ago)
Latest Published: 2021-01-04 06:41:31 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-04 06:41:31 (5 years ago)
Signed By: Dolby Laboratories, Inc.
Status: Valid

The signature on RP3DAA64.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%localappdata%\innovative solutions\drivermax\agent\restore\k325678agtbwu6sc0l2bk0xhxlll8713v5g6x2x5khh3xv4990\media\hdaudio_func_01@amp;ven_10ec@amp;dev_0887
%localappdata%\innovative solutions\drivermax\agent\restore\6y4qu2n55645y9j51ei76akbt7u1l56cbhtvnis6agu7it1so6\media\hdaudio_func_01@amp;ven_10ec@amp;dev_0662
%localappdata%\innovative solutions\drivermax\agent\uploads\578xq3ht5y6d4qux0o900gipm67gr9sc12r5ie3828j94hk172\media\hdaudio_func_01@amp;ven_10ec@amp;dev_0662
%localappdata%\innovative solutions\drivermax\agent\uploads\51164jb9t1hf2152wyb42uc1elbohsk56evg6143lur67leqe5\media

ThreatInfo has observed RP3DAA64.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

50.0%
25.0%
25.0%

The strongest geographic signal for this file is Romania with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 50.0%
Windows 7 50.0%

The most common operating system signal for RP3DAA64.dll is Windows 10 with 50.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

RP3DAA64.dll is identified as pe for 64 systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000400000
Entry Address: 0x0000b0c4

PE Sections:

Name Size of data MD5
.text 52224 0796dcf7c2e5e0d7837ea6324423664a
.data 1024 4b2fde64c72c12f003b4e3d87b85755e
.pdata 3072 e6306da86ef79ce7d4607d6761041b46
.rsrc 245760 f6dcfc43d63f63088ab588a26de982cf
.reloc 1536 67c4269525c792024baf80c91ea5880b

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

More information: