GridinSoft Threat Intelligence
aegen.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2020-12-04 00:42:12 (5 years ago); latest analysis 2024-06-20 23:00:44 (2 years ago).
Company metadata: Avira Operations GmbH & Co. KG. Product metadata: AVGEN.
Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.
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
aegen.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVGEN. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2024-06-20 23:00:44 (2 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: | AVGEN |
| Company Name: | Avira Operations GmbH & Co. KG |
| MD5: | 9a11310b57b677d3c917bb9905792b54 |
| Size: | 718 KB |
| First Published: | 2020-12-04 00:42:12 (5 years ago) |
| Latest Published: | 2024-06-20 23:00:44 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-06-20 23:00:44 (2 years ago) |
Overview
| 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.
Common Places:
| %programfiles%\totalav |
| %programfiles%\scanguard |
| %sysdrive%\rei |
| %commonappdata%\restoro |
| %commonappdata%\restoro\av\avupdate_tmp_8ptutk\av4\avira1144\savapi4-ave2\win32 |
| %commonappdata%\restoro\av\avupdate_tmp_8ptutk\av4\avira1142\savapi4-ave2\win32 |
| %programfiles%\totalav\savapi |
| %commonappdata%\reimage protector |
| %programfiles%\pcprotect |
| %programfiles%\tweakbit\anti-malware |
ThreatInfo has observed aegen.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 aegen.dll across 39 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 9.3% 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 aegen.dll is Windows 10 with 75.4% 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
aegen.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.
cd9b884812f4dca39cdae6773d94664d
5dde44afcceaba412092dde5563d1e1d
8d854e2b14d7d0c26024134490b93720
657e6f513b0afde0b5b94fe1b7f43c6f
03898cdca1865d798856aec3c543b463
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.