GridinSoft Threat Intelligence

aecore.dll file report

Clean record File reputation report
MD5 60c1cdac6b30cce5ce9f5cc85de67b07
Latest seen 2021-06-09 20:36:18 (4 years ago)
First seen 2021-03-15 21:50:25 (5 years ago)
Size 282 KB
Product AVCORE

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-03-15 21:50:25 (5 years ago); latest analysis 2021-06-09 20:36:18 (4 years ago).

Publisher context

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

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.

aecore.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVCORE. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2021-06-09 20:36:18 (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: AVCORE
Company Name: Avira Operations GmbH & Co. KG
MD5: 60c1cdac6b30cce5ce9f5cc85de67b07
Size: 282 KB
First Published: 2021-03-15 21:50:25 (5 years ago)
Latest Published: 2021-06-09 20:36:18 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-06-09 20:36:18 (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%\scanguard
%sysdrive%\rei
%programfiles%\totalav

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

aecore.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 0x0002c86e
Image base 0x10000000

PE Sections:

Sections 5
Raw data 262144

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

.text 225280 bytes · 85.9% of section data
MD5 bcd12b5d1e07fb79a4e3ec5ff7c84dc4
.rdata 12288 bytes · 4.7% of section data
MD5 a20f57eaee3d699119bd35061af55962
.data 12288 bytes · 4.7% of section data
MD5 79b87774eebe6e2a862049198e0f76ba
.rsrc 4096 bytes · 1.6% of section data
MD5 f7e7093b5204660679811f20d7a9e774
.reloc 8192 bytes · 3.1% of section data
MD5 a0b71d0081845143b015575c9c99659d

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 60c1cdac6b30cce5ce9f5cc85de67b07.
  • 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.