GridinSoft Threat Intelligence

ASEng.dll file report

Under review File reputation report
MD5 c4b85b75df78378dcb3704ff5f349e0e
Latest seen 2024-01-15 23:47:48 (2 years ago)
First seen 2017-05-28 02:05:33 (8 years ago)
Size 340 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 02:05:33 (8 years ago); latest analysis 2024-01-15 23:47:48 (2 years ago).

Digital signature

Signed by WinZip Computing LLC. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

ASEng.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-01-15 23:47:48 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

MD5: c4b85b75df78378dcb3704ff5f349e0e
Size: 340 KB
First Published: 2017-05-28 02:05:33 (8 years ago)
Latest Published: 2024-01-15 23:47:48 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-15 23:47:48 (2 years ago)
Signed By: WinZip Computing LLC
Status: Valid

The signature on ASEng.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%\winzip system utilities suite
%programfiles%

ThreatInfo has observed ASEng.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 57.1%
Windows 7 35.7%
Windows 8.1 7.1%

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

ASEng.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 0x000267c3
Image base 0x10000000

PE Sections:

Sections 5
Raw data 341504

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

.text 239104 bytes · 70.0% of section data
MD5 205e410002421bec40486c0270079e29
.rdata 44544 bytes · 13.0% of section data
MD5 82731006a0c283e67dd2ab58a58e6847
.data 10752 bytes · 3.1% of section data
MD5 80bd5c93ca9d60995734117974d2876c
.rsrc 14336 bytes · 4.2% of section data
MD5 b17e9a4462ec78da60ce380dc0daf1ed
.reloc 32768 bytes · 9.6% of section data
MD5 8f6c7e3774d5679c10abb50d8e5197a0

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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