GridinSoft Threat Intelligence

aevdf.dll file report

Clean record File reputation report
MD5 f817f6fadc6309a83018045c745a0e8b
Latest seen 2022-02-28 23:56:05 (4 years ago)
First seen 2021-03-08 16:29:01 (5 years ago)
Size 153 KB
Product AVVDF

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-03-08 16:29:01 (5 years ago); latest analysis 2022-02-28 23:56:05 (4 years ago).

Publisher context

Company metadata: Avira Operations GmbH & Co. KG. Product metadata: AVVDF.

Digital signature

Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.

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.

aevdf.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVVDF. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2022-02-28 23:56:05 (4 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: AVVDF
Company Name: Avira Operations GmbH & Co. KG
MD5: f817f6fadc6309a83018045c745a0e8b
Size: 153 KB
First Published: 2021-03-08 16:29:01 (5 years ago)
Latest Published: 2022-02-28 23:56:05 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-02-28 23:56:05 (4 years ago)
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.

%commonappdata%\restoro
%programfiles%\totalav
%programfiles%\scanguard
%sysdrive%\rei

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

Windows 10 89.7%
Windows 7 10.3%

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

aevdf.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 0x000112da
Image base 0x10000000

PE Sections:

Sections 5
Raw data 131072

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

.text 102400 bytes · 78.1% of section data
MD5 61da59f02d5c9cba1bfc5311168c13d8
.rdata 8192 bytes · 6.3% of section data
MD5 4a168f9fee37c876f8b54331c61b3093
.data 8192 bytes · 6.3% of section data
MD5 3bf7e8d131618081babb99745ee784e6
.rsrc 4096 bytes · 3.1% of section data
MD5 2e9327cca315edac91ad8b8def549da2
.reloc 8192 bytes · 6.3% of section data
MD5 24fafdb36b48c625fe58d75d19fa2397

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 f817f6fadc6309a83018045c745a0e8b.
  • 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.