GridinSoft Threat Intelligence

aeoffice.dll file report

Clean record File reputation report
MD5 d99b44094639d7c344211b1c0f66bca7
Latest seen 2022-01-08 21:37:28 (4 years ago)
First seen 2021-09-02 20:33:10 (4 years ago)
Size 862 KB
Product AVOFFICE

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-09-02 20:33:10 (4 years ago); latest analysis 2022-01-08 21:37:28 (4 years ago).

Publisher context

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

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.

aeoffice.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVOFFICE. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2022-01-08 21:37:28 (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: AVOFFICE
Company Name: Avira Operations GmbH & Co. KG
MD5: d99b44094639d7c344211b1c0f66bca7
Size: 862 KB
First Published: 2021-09-02 20:33:10 (4 years ago)
Latest Published: 2022-01-08 21:37:28 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-01-08 21:37:28 (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

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 100.0%

The most common operating system signal for aeoffice.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.

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 0x0007310a
Image base 0x10000000

PE Sections:

Sections 5
Raw data 847872

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

.text 499712 bytes · 58.9% of section data
MD5 2e3664f433c1b1d0641c90456b901039
.rdata 278528 bytes · 32.9% of section data
MD5 2577682a79763f616060a3950fec93fb
.data 16384 bytes · 1.9% of section data
MD5 a9bead9b987b018551b04d55396cd747
.rsrc 4096 bytes · 0.5% of section data
MD5 8fc65e4381b8b8be30737730f9888cb2
.reloc 49152 bytes · 5.8% of section data
MD5 80838479613c1d6c288348261145a50e

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