aedroid.dll file report

MD5 9eb7aa7ca959985149f271096337293c
Latest seen 2021-02-26 16:20:22 (5 years ago)
First seen 2018-08-16 20:10:15 (7 years ago)
Size 2 MB
Product AVDROID

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-08-16 20:10:15 (7 years ago); latest analysis 2021-02-26 16:20:22 (5 years ago).

Publisher context

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

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.

aedroid.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVDROID. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Clean, based on the latest analysis from 2021-02-26 16:20:22 (5 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: AVDROID
Company Name: Avira Operations GmbH @amp; Co. KG
MD5: 9eb7aa7ca959985149f271096337293c
Size: 2 MB
First Published: 2018-08-16 20:10:15 (7 years ago)
Latest Published: 2021-02-26 16:20:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-26 16:20:22 (5 years ago)
Signed By: Avira Operations GmbH @amp; Co. KG
Status: Valid

The signature on aedroid.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%\totalav
%programfiles%\auslogics anti-malware
%programfiles%\auslogics\anti-malware
%sysdrive%\rei
%commonappdata%\restoro
%programfiles%\scanguard
%commonappdata%\reimage protector
%programfiles%\tweakbit\anti-malware
%programfiles%\totalav\savapi\avupdate_backup\ave2\win32
%programfiles%\totalav

ThreatInfo has observed aedroid.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.

17.9%
10.4%
9.5%
5.5%
5.5%
5.0%
4.0%
3.5%
3.5%
3.5%
3.0%
3.0%
2.5%
2.5%
2.5%
2.5%
1.5%
1.5%
1.5%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%

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

Windows 10 61.4%
Windows 7 30.2%
Windows 8.1 6.9%
Windows Vista 1.0%
Windows XP 0.5%

The most common operating system signal for aedroid.dll is Windows 10 with 61.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.

aedroid.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: 0x00017f24

PE Sections:

Name Size of data MD5
.text 139264 8508fb0c57d32ef95b0d5dbd5589ac71
.rdata 32768 62d501ee28f7530c900f80467624d44e
.data 2551808 84d6e9b2648a9af444813f5920eaa059
.rsrc 4096 e756ac2c8fd5a6c1b0793de0a1f7403e
.reloc 16384 67784728d1034bf96a40dd3f1985755e

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: