aemobile.dll file report

MD5 1fd614814be6f5ef098f9854f0f3b487
Latest seen 2023-02-06 23:31:25 (3 years ago)
First seen 2017-05-31 13:04:02 (8 years ago)
Size 337 KB
Product AVMOBILE

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-31 13:04:02 (8 years ago); latest analysis 2023-02-06 23:31:25 (3 years ago).

Publisher context

Company metadata: Avira Operations GmbH @amp; Co. KG. Product metadata: AVMOBILE.

Digital signature

Signed by Avira Operations GmbH @amp; Co. KG. The signature is reported as valid, but signed files can still be bundled or abused.

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.

aemobile.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVMOBILE. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Clean, based on the latest analysis from 2023-02-06 23:31:25 (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.

Product Name: AVMOBILE
Company Name: Avira Operations GmbH @amp; Co. KG
MD5: 1fd614814be6f5ef098f9854f0f3b487
Size: 337 KB
First Published: 2017-05-31 13:04:02 (8 years ago)
Latest Published: 2023-02-06 23:31:25 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-02-06 23:31:25 (3 years ago)
Signed By: Avira Operations GmbH @amp; Co. KG
Status: Valid

The signature on aemobile.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.

%programfiles%\psafe\total\deepscan\sdeng\savapi
%sysdrive%\rei\av
%programfiles%\elex-tech\yac\avira\antivirus\defs_20161116_00
%programfiles%\scanguard\savapi
%programfiles%\scanguard\savapi\avupdate_backup\ave2\win32\int
%programfiles%\psafe\total\deepscan\temp\savapi
%programfiles%\essentware\pckav\engine
%programfiles%\psafe\total\deepscan\sdeng
%programfiles%\pcprotect
%commonappdata%\reimage protector

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.

30.4%
21.7%
6.5%
4.3%
4.3%
4.3%
4.3%
4.3%
2.2%
2.2%
2.2%
2.2%
2.2%
2.2%
2.2%
2.2%
2.2%

The strongest geographic signal for this file is United States with 30.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 43.5%
Windows 8.1 28.3%
Windows 10 23.9%
Windows Vista 4.3%

The most common operating system signal for aemobile.dll is Windows 7 with 43.5% 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.

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: 0x000393e0

PE Sections:

Name Size of data MD5
.text 278528 f11d8dacae62614846ab03bbf775bf0a
.rdata 20480 ef755f99298cbc433bcbfae908d62708
.data 20480 e5e358594a8187c81b815c973d4e8b91
.rsrc 4096 482c949bd1fcb6c1cd2a789d8d6a8f4b
.reloc 12288 9fac7e8e4d3b0cb64aa5c61eb7d56d39

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: