GridinSoft Threat Intelligence

aeoffice.dll file report

Clean record File reputation report
MD5 20b2ad5b564695b05fa4a4be2507ee14
Latest seen 2022-12-22 23:55:32 (3 years ago)
First seen 2018-01-16 14:08:17 (8 years ago)
Size 653 KB
Product AVOFFICE

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-01-16 14:08:17 (8 years ago); latest analysis 2022-12-22 23:55:32 (3 years ago).

Publisher context

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

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.

aeoffice.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVOFFICE. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Clean, based on the latest analysis from 2022-12-22 23:55:32 (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: AVOFFICE
Company Name: Avira Operations GmbH @amp; Co. KG
MD5: 20b2ad5b564695b05fa4a4be2507ee14
Size: 653 KB
First Published: 2018-01-16 14:08:17 (8 years ago)
Latest Published: 2022-12-22 23:55:32 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-12-22 23:55:32 (3 years ago)
Signed By: Avira Operations GmbH @amp; Co. KG
Status: Valid

The signature on aeoffice.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
%sysdrive%\rei
%programfiles%\scanguard
%sysdrive%\rei\av\avupdate_tmp_bu4frl\av4\avira115\ave2\win32
%programfiles%\pcprotect
%programfiles%\auslogics\anti-malware

ThreatInfo has observed aeoffice.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 66.4%
Windows 7 19.2%
Windows 8 7.2%
Windows 8.1 4.0%
Windows XP 2.4%
Windows Vista 0.8%

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

aeoffice.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 0x000589ca
Image base 0x10000000

PE Sections:

Sections 5
Raw data 638976

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

.text 393216 bytes · 61.5% of section data
MD5 95cf081d0fdf8214d78ab7833c9c4cbe
.rdata 188416 bytes · 29.5% of section data
MD5 c98a0b3dafe8bb5f50fc7f3f145dc558
.data 12288 bytes · 1.9% of section data
MD5 1e79828d5ad1a7dfd6399af45ad0c3f5
.rsrc 4096 bytes · 0.6% of section data
MD5 8f1eabd9f02dd984975e3dc0c7ed58a6
.reloc 40960 bytes · 6.4% of section data
MD5 813c4e68a354095adc1dc38ceba094f8

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 20b2ad5b564695b05fa4a4be2507ee14.
  • 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.