GridinSoft Threat Intelligence

aerdl.dll file report

Clean record File reputation report
MD5 8d3b5f9d2f0a0822b107610ec481e1ac
Latest seen 2021-10-26 20:47:13 (4 years ago)
First seen 2021-04-28 20:15:50 (5 years ago)
Size 1 MB
Product AVRDL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-04-28 20:15:50 (5 years ago); latest analysis 2021-10-26 20:47:13 (4 years ago).

Publisher context

Company metadata: Avira Operations GmbH & Co. KG. Product metadata: AVRDL.

Digital signature

Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

aerdl.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVRDL. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2021-10-26 20:47:13 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: AVRDL
Company Name: Avira Operations GmbH & Co. KG
MD5: 8d3b5f9d2f0a0822b107610ec481e1ac
Size: 1 MB
First Published: 2021-04-28 20:15:50 (5 years ago)
Latest Published: 2021-10-26 20:47:13 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-10-26 20:47:13 (4 years ago)
Signed By: Avira Operations GmbH & Co. KG
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\totalav
%commonappdata%\restoro
%sysdrive%\rei

ThreatInfo has observed aerdl.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 10 84.6%
Windows 7 15.4%

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

aerdl.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x000e3828
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1249280

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

.text 983040 bytes · 78.7% of section data
MD5 a3ef9fcce941d3e6a5348d8a4b9d8341
.rdata 53248 bytes · 4.3% of section data
MD5 e36a64ff1b9124ee53b374fa5cd3b97e
.data 180224 bytes · 14.4% of section data
MD5 5487d37003d4345d7497e430f33848f1
.rsrc 4096 bytes · 0.3% of section data
MD5 d6f6626be0e7b1194f3497c26c0e139f
.reloc 28672 bytes · 2.3% of section data
MD5 12a8562306cfe3ae265c2d9b5c00ca79

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 8d3b5f9d2f0a0822b107610ec481e1ac.
  • 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.