GridinSoft Threat Intelligence

DolbyDAX2APOv211.dll file report

Under review File reputation report
MD5 d2c3b6c9a024118b43835b9d874efeef
Latest seen 2021-01-04 13:52:11 (5 years ago)
First seen 2020-06-27 06:47:03 (5 years ago)
Size 5 MB
Publisher Dolby Laboratories
Product Dolby DAX2

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-06-27 06:47:03 (5 years ago); latest analysis 2021-01-04 13:52:11 (5 years ago).

Publisher context

Company metadata: Dolby Laboratories. Product metadata: Dolby DAX2.

Digital signature

Signed by Dolby Laboratories, Inc.;Microsoft Windows Hardware Compatibility Publisher. 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.

DolbyDAX2APOv211.dll is a Windows file recorded in the ThreatInfo database. It is associated with Dolby DAX2. The reported company name is Dolby Laboratories. The current detection status is Undefined, based on the latest analysis from 2021-01-04 13:52:11 (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 DAX2
Company Name: Dolby Laboratories
MD5: d2c3b6c9a024118b43835b9d874efeef
Size: 5 MB
First Published: 2020-06-27 06:47:03 (5 years ago)
Latest Published: 2021-01-04 13:52:11 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-04 13:52:11 (5 years ago)

The signature on DolbyDAX2APOv211.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.

%commonappdata%\reviversoft\driver reviver\downloads\80
%commonappdata%\reviversoft\driver reviver\downloads\96fffcb1-222d-475b-b3de-562928746539
%commonappdata%\reviversoft\driver reviver\downloads\111
%commonappdata%\reviversoft\driver reviver\downloads\62
%commonappdata%\reviversoft\driver reviver\downloads\cbc7092c-c4f9-4d65-b84c-c1623ee81d77
%commonappdata%\reviversoft\driver reviver\downloads\18
%commonappdata%\winzip\winzip driver updater\downloads\46
%commonappdata%\winzip\winzip driver updater\downloads\48db1056-6685-4a17-8ba9-aad318465a4d

ThreatInfo has observed DolbyDAX2APOv211.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.

Windows 7 70.0%
Windows 10 30.0%

The most common operating system signal for DolbyDAX2APOv211.dll is Windows 7 with 70.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.

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

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x003051ec
Image base 0x0000000180000000

PE Sections:

Sections 14
Raw data 5275136

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 3356160 bytes · 63.6% of section data
MD5 f5a23774de15a122afb5094cb0a39f5e
RT_CODE 1024 bytes · 0.0% of section data
Uncommon name
MD5 7ef5997b5e74b1f87fb4c57c3c049818
IPPCODE 837632 bytes · 15.9% of section data
Uncommon name
MD5 ace68b294d93444d9b53219f3ab16ce4
RT_BSS 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rdata 916480 bytes · 17.4% of section data
MD5 68f825877794c2bd1d17a16b73c978e2
.data 28160 bytes · 0.5% of section data
MD5 802d9e530296c7de397179a57ddde7cf
.pdata 86016 bytes · 1.6% of section data
MD5 bcc125094fcf9b5d9a30a50eb65d3e7c
RT_CONST 1024 bytes · 0.0% of section data
Uncommon name
MD5 08dc112c323f07a3b3839ace910ccb52
RT_DATA 1536 bytes · 0.0% of section data
Uncommon name
MD5 eabcc41c1cb6674d4c107e6ba84398b5
.trace 9728 bytes · 0.2% of section data
Uncommon name
MD5 b927d75e19411b23ba0696d0f9850d7b
_RDATA 4608 bytes · 0.1% of section data
Uncommon name
MD5 fd42238dedbd57a14235c982351ec482
IPPDATA 5120 bytes · 0.1% of section data
Uncommon name
MD5 d90371a3286771ce4cc05b282093eeef
.rsrc 13312 bytes · 0.3% of section data
MD5 7d943da304baf9ef2bb015475c6a49a0
.reloc 14336 bytes · 0.3% of section data
MD5 b2567966a805c4a3fd7a913e0ebcb9ae

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.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with d2c3b6c9a024118b43835b9d874efeef.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.