GridinSoft Threat Intelligence

aeml.dll file report

Clean record File reputation report
MD5 e0aafc540e0ae239076b56bce6500d4d
Latest seen 2021-08-12 20:38:43 (4 years ago)
First seen 2021-08-12 20:38:43 (4 years ago)
Size 370 KB
Product AVML

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-08-12 20:38:43 (4 years ago); latest analysis 2021-08-12 20:38:43 (4 years ago).

Publisher context

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

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.

aeml.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVML. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2021-08-12 20:38:43 (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: AVML
Company Name: Avira Operations GmbH & Co. KG
MD5: e0aafc540e0ae239076b56bce6500d4d
Size: 370 KB
First Published: 2021-08-12 20:38:43 (4 years ago)
Latest Published: 2021-08-12 20:38:43 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-08-12 20:38:43 (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%\outbyte\avarmor

ThreatInfo has observed aeml.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 100.0%

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

aeml.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 0x0000fcd0
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 352768

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

.text 103424 bytes · 29.3% of section data
MD5 bf006d64432ec6a0b11e0f473c640eab
.rdata 230400 bytes · 65.3% of section data
MD5 cf06f8527454115faff6c55d7c8164a0
.data 6144 bytes · 1.7% of section data
MD5 561407999915bcf7438adf6cad7e9aa5
.pdata 9216 bytes · 2.6% of section data
MD5 f6ffb79601e03d5f512e97b597c9216d
.rsrc 1536 bytes · 0.4% of section data
MD5 06dc1d7fd8e6deb16ae70f5b8b11ff2e
.reloc 2048 bytes · 0.6% of section data
MD5 c8bbf64fa2a99594d4b9368cd66dc822

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