GridinSoft Threat Intelligence

aescript.dll file report

Clean record File reputation report
MD5 44c54a0fd5a5c645f94fb4cead842b8d
Latest seen 2023-04-20 23:27:39 (3 years ago)
First seen 2020-03-23 15:36:55 (6 years ago)
Size 1 MB
Product AVSCRIPT

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-03-23 15:36:55 (6 years ago); latest analysis 2023-04-20 23:27:39 (3 years ago).

Publisher context

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

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.

aescript.dll is a Windows file recorded in the ThreatInfo database. It is associated with AVSCRIPT. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2023-04-20 23:27:39 (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: AVSCRIPT
Company Name: Avira Operations GmbH & Co. KG
MD5: 44c54a0fd5a5c645f94fb4cead842b8d
Size: 1 MB
First Published: 2020-03-23 15:36:55 (6 years ago)
Latest Published: 2023-04-20 23:27:39 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-04-20 23:27:39 (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.

%commonappdata%\restoro
%sysdrive%\rei
%commonappdata%\innovative solutions

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

aescript.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 0x000e2d0c
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1163264

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

.text 974848 bytes · 83.8% of section data
MD5 1b24d7e9b81a6951c37016787e6766e7
.rdata 106496 bytes · 9.2% of section data
MD5 3c716bc0e018902087565bce1ad5b28b
.data 61440 bytes · 5.3% of section data
MD5 c38dd33c1c12f291debc79e941ce0eac
.rsrc 4096 bytes · 0.4% of section data
MD5 a528c875593ae4e1c64df1d71ad824ec
.reloc 16384 bytes · 1.4% of section data
MD5 ccae21ee26e035e1e559fcff5408cc4c

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 44c54a0fd5a5c645f94fb4cead842b8d.
  • 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.