GridinSoft Threat Intelligence

aedroid.dll file report

Clean record File reputation 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
Publisher Avira Operations GmbH @amp; Co. KG
Product AVDROID
Signed by Avira Operations GmbH @amp; Co. KG

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.

File context

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.

File Details

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)

Overview

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.

Common Places:

%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

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.

Geographic signal

Observed country distribution

ThreatInfo has seen aedroid.dll across 35 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 17.9%
Low High activity

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.

OS Version:

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.

Analysis

aedroid.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00017f24
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2744320

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 139264 bytes · 5.1% of section data
MD5 8508fb0c57d32ef95b0d5dbd5589ac71
.rdata 32768 bytes · 1.2% of section data
MD5 62d501ee28f7530c900f80467624d44e
.data 2551808 bytes · 93.0% of section data
MD5 84d6e9b2648a9af444813f5920eaa059
.rsrc 4096 bytes · 0.1% of section data
MD5 e756ac2c8fd5a6c1b0793de0a1f7403e
.reloc 16384 bytes · 0.6% of section data
MD5 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.

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 9eb7aa7ca959985149f271096337293c.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.