GridinSoft Threat Intelligence

DolbyDAX2APOvlldp.dll file report

Under review File reputation report
MD5 b5356e44367489b1b1ff73cce4ee93a3
Latest seen 2021-01-02 12:40:15 (5 years ago)
First seen 2019-12-01 03:08:55 (6 years ago)
Size 1 MB
Publisher Dolby Laboratories
Product Dolby DAX2
Signed by Dolby Laboratories, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-12-01 03:08:55 (6 years ago); latest analysis 2021-01-02 12:40:15 (5 years ago).

Publisher context

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

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.

File context

DolbyDAX2APOvlldp.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-02 12:40:15 (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.

File Details

Product Name: Dolby DAX2
Company Name: Dolby Laboratories
MD5: b5356e44367489b1b1ff73cce4ee93a3
Size: 1 MB
First Published: 2019-12-01 03:08:55 (6 years ago)
Latest Published: 2021-01-02 12:40:15 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-02 12:40:15 (5 years ago)

Overview

Signed By: Dolby Laboratories, Inc.
Status: Valid

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

Common Places:

%commonappdata%\reviversoft\pc reviver\s-1-5-21-2927450747-2507301955-2091121292-1001\driver updater\downloads\2c1ae552-2137-4f0f-a13e-5da64ef8b93c
%commonappdata%\reviversoft\pc reviver\s-1-5-21-2927450747-2507301955-2091121292-1001\driver updater\downloads\53
%localappdata%\innovative solutions\drivermax\agent\uploads\066d08f813a8sw17yfgt2j4t2774w18n318990ifmm951wrpf5\media
%localappdata%\innovative solutions\drivermax\agent\restore\u67ew66793h30uoq7y54tjhavi9wn929qx2w7284y822m2cbnq\media

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

Geographic signal

Observed country distribution

ThreatInfo has seen DolbyDAX2APOvlldp.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Saudi Arabia
Share 60.0%
Low High activity

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

OS Version:

Windows 10 100.0%

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

Analysis

DolbyDAX2APOvlldp.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 0x0006ca1c
Image base 0x0000000180000000

PE Sections:

Sections 14
Raw data 1227264

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

.text 798208 bytes · 65.0% of section data
MD5 2adbc574f315532f2c80ff29788b70cf
RT_CODE 2048 bytes · 0.2% of section data
Uncommon name
MD5 b25ecdbc7f1e5373b497feea8fc6fd7a
RT_BSS 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rdata 319488 bytes · 26.0% of section data
MD5 cc943f87369eeeb537320802d2e2eeaf
.data 22528 bytes · 1.8% of section data
MD5 ee337b19e1562c29e93065326ce95aa6
.pdata 44544 bytes · 3.6% of section data
MD5 1e4e14fa5bc77474829f1f6da565fb97
RT_CONST 1024 bytes · 0.1% of section data
Uncommon name
MD5 f2ac0cf5552289e26903b7f6c0777d0f
RT_DATA 1536 bytes · 0.1% of section data
Uncommon name
MD5 eabcc41c1cb6674d4c107e6ba84398b5
.gfids 2560 bytes · 0.2% of section data
Uncommon name
MD5 2b8c546f73e1e4667d9b2891c5217f5d
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.trace 9216 bytes · 0.8% of section data
Uncommon name
MD5 d777460ff30ec20360a9b4907efe38e9
_RDATA 4608 bytes · 0.4% of section data
Uncommon name
MD5 87d667b7870ff833028cc4e310b73623
.rsrc 13312 bytes · 1.1% of section data
MD5 f8f8589fbe9f7d8a9c2853ce67cefc60
.reloc 7680 bytes · 0.6% of section data
MD5 d459bbd31cf95cd5ea2aabb129062727

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 b5356e44367489b1b1ff73cce4ee93a3.
  • 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.