aemobile.dll file report
ThreatInfo file report
aemobile.dll
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2021-11-15 21:49:01 (4 years ago); latest analysis 2022-11-16 23:37:23 (3 years ago).
Company metadata: Avira Operations GmbH & Co. KG. Product metadata: AVMOBILE.
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
aemobile.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVMOBILE. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2022-11-16 23:37:23 (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: | AVMOBILE |
| Company Name: | Avira Operations GmbH & Co. KG |
| MD5: | 10678c99abd66dd6b6df79ac9a2bdf90 |
| Size: | 365 KB |
| First Published: | 2021-11-15 21:49:01 (4 years ago) |
| Latest Published: | 2022-11-16 23:37:23 (3 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2022-11-16 23:37:23 (3 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%\totalav |
| %programfiles%\totalav |
| %sysdrive%\rei |
| %programfiles%\totalav |
| %programfiles%\totalav |
| %commonappdata%\restoro |
| %appdata%\shield antivirus |
| %appdata%\shield antivirus |
| %commonappdata%\restoro |
ThreatInfo has observed aemobile.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.
Geography:
| 10.0% | ||
| 10.0% | ||
| 7.5% | ||
| 7.5% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% | ||
| 2.5% |
The strongest geographic signal for this file is United States with 10.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 10 | 88.1% | |
| Windows 7 | 9.5% | |
| Windows 8.1 | 2.4% |
The most common operating system signal for aemobile.dll is Windows 10 with 88.1% 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
aemobile.dll is identified as pe for 32 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.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x10000000 |
| Entry Address: | 0x0003668f |
PE Sections:
| Name | Size of data | MD5 |
| .text | 283648 | eaf2e082fecf02672806a4e1ed877659 |
| .rdata | 35840 | b98dc7dafbc85458025f255913da35dd |
| .data | 16896 | b5dea8c881341d307d0188ba2ab984a9 |
| .rsrc | 1536 | 58e7e5a6f9594bffa03c61690bd06f76 |
| .reloc | 9216 | 9500ef24047905858a54ef19cff7b53d |
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.
More information:
