GridinSoft Threat Intelligence

aeemu.dll file report

Clean record File reputation report
MD5 a6c22949c0fa59a97434115c4c95186e
Latest seen 2021-08-12 20:26:06 (4 years ago)
First seen 2021-08-12 20:26:06 (4 years ago)
Size 535 KB
Product AVEMU

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

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

Publisher context

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

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.

aeemu.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVEMU. 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:26:06 (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: AVEMU
Company Name: Avira Operations GmbH & Co. KG
MD5: a6c22949c0fa59a97434115c4c95186e
Size: 535 KB
First Published: 2021-08-12 20:26:06 (4 years ago)
Latest Published: 2021-08-12 20:26:06 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-08-12 20:26:06 (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 aeemu.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 aeemu.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.

aeemu.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 0x00062110
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 518656

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

.text 440832 bytes · 85.0% of section data
MD5 d1f9385b1d873e7e76c34b529c700f2f
.rdata 32256 bytes · 6.2% of section data
MD5 9bc804500bba7f566f78de67b7512f61
.data 23040 bytes · 4.4% of section data
MD5 b7900130786bb34d4322d7fbcd750602
.pdata 14848 bytes · 2.9% of section data
MD5 3e0815bc5fd696f9331f9da909d65e8f
.rsrc 1536 bytes · 0.3% of section data
MD5 632be9d09c5d28bfb93fb95d77f0ddea
.reloc 6144 bytes · 1.2% of section data
MD5 d7effa655f28ccf74641608bcb7e8c75

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