GridinSoft Threat Intelligence

R4EED64A.dll file report

Under review File reputation report
MD5 245fb746cab8396e1d5674e930eb58b1
Latest seen 2021-01-04 14:33:38 (5 years ago)
First seen 2020-06-27 06:47:28 (5 years ago)
Size 442 KB
Publisher Dolby Laboratories
Product Dolby PCEE4 COM DLL
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 2020-06-27 06:47:28 (5 years ago); latest analysis 2021-01-04 14:33:38 (5 years ago).

Publisher context

Company metadata: Dolby Laboratories. Product metadata: Dolby PCEE4 COM DLL.

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

R4EED64A.dll is a Windows file recorded in the ThreatInfo database. It is associated with Dolby PCEE4 COM DLL. The reported company name is Dolby Laboratories. The current detection status is Undefined, based on the latest analysis from 2021-01-04 14:33:38 (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 PCEE4 COM DLL
Company Name: Dolby Laboratories
MD5: 245fb746cab8396e1d5674e930eb58b1
Size: 442 KB
First Published: 2020-06-27 06:47:28 (5 years ago)
Latest Published: 2021-01-04 14:33:38 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-04 14:33:38 (5 years ago)

Overview

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

The signature on R4EED64A.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\driver reviver\downloads\96fffcb1-222d-475b-b3de-562928746539
%commonappdata%\reviversoft\driver reviver\downloads\80
%localappdata%\innovative solutions\drivermax\agent\uploads\t2kh8ln445484r16kxd8945tmtx9ux6j53s9lx744lt25a8045\media
%localappdata%\innovative solutions\drivermax\agent\uploads\398o14f02lw568m3nb20e65lf06363cy3106bq8jgg78ds2844\media
%commonappdata%\reviversoft\driver reviver\downloads\66
%commonappdata%\reviversoft\driver reviver\downloads\e746e057-0f99-442d-b3fe-881db49c8496
%commonappdata%\reviversoft\driver reviver\downloads\cbc7092c-c4f9-4d65-b84c-c1623ee81d77
%commonappdata%\reviversoft\driver reviver\downloads\62
%commonappdata%\reviversoft\driver reviver\downloads\18
%commonappdata%\winzip\winzip driver updater\downloads\46

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

Top country China
Share 28.6%
Low High activity

The strongest geographic signal for this file is China with 28.6% 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 50.0%
Windows 7 50.0%

The most common operating system signal for R4EED64A.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.

Analysis

R4EED64A.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 0x0000dcbc
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 427520

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

.text 89088 bytes · 20.8% of section data
MD5 78daf9f2ff6a10e81a74c6d8874c0414
RT_CODE 246272 bytes · 57.6% of section data
Uncommon name
MD5 2f953e69af755458f0154e85de7185e1
RT_BSS 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.data 2048 bytes · 0.5% of section data
MD5 7bcf1401a83ec23120145d65f2f2623d
.pdata 13312 bytes · 3.1% of section data
MD5 f1464e7db32f1baaf95d525b93c29946
RT_CONST 51712 bytes · 12.1% of section data
Uncommon name
MD5 a7bf16815158ebcb93d23f504b370fd6
RT_DATA 1024 bytes · 0.2% of section data
Uncommon name
MD5 d0dbd31d674df6d124c165a8cd714317
.rsrc 19968 bytes · 4.7% of section data
MD5 b6fd66860b4ddb4c2339d36de422d3e1
.reloc 4096 bytes · 1.0% of section data
MD5 d3cf3d06b57dc7606757b07b7a15272a

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 245fb746cab8396e1d5674e930eb58b1.
  • 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.