GridinSoft Threat Intelligence
aeemu_IObitDel.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-10-30 13:13:04 (8 years ago); latest analysis 2023-04-09 23:59:40 (3 years ago).
Company metadata: Avira Operations GmbH @amp; Co. KG. Product metadata: AVEMU.
Signed by Avira Operations GmbH @amp; Co. KG. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
aeemu_IObitDel.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVEMU. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Clean, based on the latest analysis from 2023-04-09 23:59:40 (3 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.
File Details
| Product Name: | AVEMU |
| Company Name: | Avira Operations GmbH @amp; Co. KG |
| MD5: | c147954ad962c8845b3d545a01300e6e |
| Size: | 410 KB |
| First Published: | 2017-10-30 13:13:04 (8 years ago) |
| Latest Published: | 2023-04-09 23:59:40 (3 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2023-04-09 23:59:40 (3 years ago) |
Overview
| Signed By: | Avira Operations GmbH @amp; Co. KG |
| Status: | Valid |
The signature on aeemu_IObitDel.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%\reimage protector\av |
| %sysdrive%\rei\av |
| %programfiles%\totalav\savapi |
| %programfiles%\sheed antivirus |
| %programfiles%\essentware\pckav\engine |
| %programfiles%\scanguard\savapi |
| %programfiles%\tweakbit\anti-malware\engine |
| %programfiles%\totalav |
| %programfiles%\scanguard |
| %sysdrive%\rei |
ThreatInfo has observed aeemu_IObitDel.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.
File Names:
2 observed namesThis hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geographic signal
Observed country distribution
ThreatInfo has seen aeemu_IObitDel.dll across 72 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 16.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for aeemu_IObitDel.dll is Windows 10 with 69.8% 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
aeemu_IObitDel.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
0e70e906ca4604a7beda21438343a760
d38a9b6e72bbfc1a32b997957974c01b
598347be5fa4c138af195b48dd9b0696
a5b68dbc8a11bb5b859f9e0a0a0630d4
fc49227bc5fe0aa66029935dd1ebfff3
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.