GridinSoft Threat Intelligence

R4EEL64A.dll file report

Under review File reputation report
MD5 2d6463b55cd67a221e605a851fd75c12
Latest seen 2023-04-21 23:41:32 (3 years ago)
First seen 2023-04-21 23:41:32 (3 years ago)
Size 154 KB
Publisher Dolby Laboratories
Product Dolby PCEE4 LFX APO
Signed by Dolby Laboratories, Inc.;Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-04-21 23:41:32 (3 years ago); latest analysis 2023-04-21 23:41:32 (3 years ago).

Publisher context

Company metadata: Dolby Laboratories. Product metadata: Dolby PCEE4 LFX APO.

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.

File context

R4EEL64A.dll is a Windows file recorded in the ThreatInfo database. It is associated with Dolby PCEE4 LFX APO. The reported company name is Dolby Laboratories. The current detection status is Undefined, based on the latest analysis from 2023-04-21 23:41:32 (3 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 PCEE4 LFX APO
Company Name: Dolby Laboratories
MD5: 2d6463b55cd67a221e605a851fd75c12
Size: 154 KB
First Published: 2023-04-21 23:41:32 (3 years ago)
Latest Published: 2023-04-21 23:41:32 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-04-21 23:41:32 (3 years ago)

Overview

Signed By: Dolby Laboratories, Inc.;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

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

%appdata%\driverpack cloud\unpack\realtek-forced-10x64-9273_conexant-drp\realtek\forced\10x64

ThreatInfo has observed R4EEL64A.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 R4EEL64A.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 100.0%
Low High activity

The strongest geographic signal for this file is Russian Federation with 100.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 R4EEL64A.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

R4EEL64A.dll is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x0000eb78
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 134144

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

.text 97280 bytes · 72.5% of section data
MD5 ca574d7e7039bcbef2a8ff7b5d1b51ec
.orpc 512 bytes · 0.4% of section data
Uncommon name
MD5 75f25b6177af3b06ba5008a8bc1236b1
RT_CODE 10240 bytes · 7.6% of section data
Uncommon name
MD5 5f2c66c07ab37b8f27893fb4b3587bbf
.data 2560 bytes · 1.9% of section data
MD5 f4fd5acc2ef93d2d498debd2c9fdd095
.pdata 5120 bytes · 3.8% of section data
MD5 08ab80e3e3058ab610714cc734cff663
RT_DATA 1536 bytes · 1.1% of section data
Uncommon name
MD5 53e979547d8c2ea86560ac45de08ae25
.rsrc 13824 bytes · 10.3% of section data
MD5 25cee1220ec1fa8ea99d9b61eb74ca65
.reloc 3072 bytes · 2.3% of section data
MD5 a87e1fc94ac064b7121ecc9f3ed5e739

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 2d6463b55cd67a221e605a851fd75c12.
  • 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.