aedroid.dll file report

MD5 13e0696fadcce65343f547ec0844a1cc
Latest seen 2026-04-18 23:00:50 (2 weeks ago)
First seen 2025-07-11 23:01:33 (10 months ago)
Size 2 MB
Product AVDROID

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-07-11 23:01:33 (10 months ago); latest analysis 2026-04-18 23:00:50 (2 weeks ago).

Publisher context

Company metadata: Avira Operations GmbH. Product metadata: AVDROID.

Digital signature

Signed by Avira Operations GmbH. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

aedroid.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVDROID. The reported company name is Avira Operations GmbH. The current detection status is Undefined, based on the latest analysis from 2026-04-18 23:00:50 (2 weeks ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: AVDROID
Company Name: Avira Operations GmbH
MD5: 13e0696fadcce65343f547ec0844a1cc
Size: 2 MB
First Published: 2025-07-11 23:01:33 (10 months ago)
Latest Published: 2026-04-18 23:00:50 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-04-18 23:00:50 (2 weeks ago)
Signed By: Avira Operations GmbH
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%\outbyte\avarmor\5.x
%programfiles%\outbyte\avarmor\5.x
%programfiles%\totalav\endpoint protection sdk\updatebackup\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk
%programfiles%\totalav\endpoint protection sdk\updatebackup\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk
%programfiles%\totalav\endpoint protection sdk\coresdk

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.

59.1%
13.6%
9.1%
4.5%
4.5%
4.5%
4.5%

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

Windows 10 100.0%

The most common operating system signal for aedroid.dll is Windows 10 with 100.0% 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 64 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: 64
Image Base: 0x0000000180000000
Entry Address: 0x00020530

PE Sections:

Name Size of data MD5
.text 220160 5874e9afe04eda206f1611e683c3d8c1
.rdata 80384 7e4b16a15ebf742e5b25256cfb371aeb
.data 2554368 42b9a64458ce8b25e11acc6dbd8b7f53
.pdata 11776 a6c44afea52c35cb2a6f6bae34556539
.fptable 512 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 0e1a7d7cab533f85a6208efa545163c0
.reloc 3072 fd920e63fa2b887c7024515586079881

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: