GridinSoft Threat Intelligence

aescn.dll file report

Clean record File reputation report
MD5 1d5a720e5b700c79cfda5c520dab000b
Latest seen 2022-10-01 23:11:57 (3 years ago)
First seen 2022-02-03 21:50:42 (4 years ago)
Size 169 KB
Product AVSCN

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-02-03 21:50:42 (4 years ago); latest analysis 2022-10-01 23:11:57 (3 years ago).

Publisher context

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

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.

aescn.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVSCN. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2022-10-01 23:11:57 (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: AVSCN
Company Name: Avira Operations GmbH & Co. KG
MD5: 1d5a720e5b700c79cfda5c520dab000b
Size: 169 KB
First Published: 2022-02-03 21:50:42 (4 years ago)
Latest Published: 2022-10-01 23:11:57 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-10-01 23:11:57 (3 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.

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

ThreatInfo has observed aescn.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 86.4%
Windows 7 13.6%

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

aescn.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 0x00011713
Image base 0x10000000

PE Sections:

Sections 5
Raw data 148480

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

.text 109568 bytes · 73.8% of section data
MD5 4ec4faf393c0cdf9cc93b6fa7e278a21
.rdata 26624 bytes · 17.9% of section data
MD5 77982abd8e66552be16fac5ffa1b1b15
.data 5632 bytes · 3.8% of section data
MD5 40bd253cc9511b5e0d8a52619aa2bc4d
.rsrc 1536 bytes · 1.0% of section data
MD5 1b50c5161f2c0b7e962c1e14f0d3a8f2
.reloc 5120 bytes · 3.4% of section data
MD5 4219d58586a079d4929b1dd2e1da3359

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 1d5a720e5b700c79cfda5c520dab000b.
  • 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.