GridinSoft Threat Intelligence

aspcomm.dll file report

Under review File reputation report
MD5 9bc04ed0a9e568f55932f8a8357fdf62
Latest seen 2024-01-15 23:44:07 (2 years ago)
First seen 2017-05-28 02:05:37 (8 years ago)
Size 216 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 02:05:37 (8 years ago); latest analysis 2024-01-15 23:44:07 (2 years ago).

Publisher context

Company metadata: TODO: <Company name>. Product metadata: TODO: <Product name>.

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.

aspcomm.dll is a Windows file recorded in the ThreatInfo database. It is associated with TODO: <Product name>. The reported company name is TODO: <Company name>. The current detection status is Undefined, based on the latest analysis from 2024-01-15 23:44:07 (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.

Product Name: TODO: <Product name>
Company Name: TODO: <Company name>
MD5: 9bc04ed0a9e568f55932f8a8357fdf62
Size: 216 KB
First Published: 2017-05-28 02:05:37 (8 years ago)
Latest Published: 2024-01-15 23:44:07 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-15 23:44:07 (2 years ago)
Signed By: WinZip Computing LLC
Status: Valid

The signature on aspcomm.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 aspcomm.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 66.7%
Windows 7 25.0%
Windows 8.1 8.3%

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

aspcomm.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 0x0000f6c3
Image base 0x10000000

PE Sections:

Sections 5
Raw data 214528

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

.text 127488 bytes · 59.4% of section data
MD5 0df1729c323f6ada00698009a2754c07
.rdata 32768 bytes · 15.3% of section data
MD5 c24ac820a60ec4788b3a322638e073b1
.data 10752 bytes · 5.0% of section data
MD5 175b0433c36afe73faf1a186fd9b4f92
.rsrc 15360 bytes · 7.2% of section data
MD5 91b77a41ca77343fb3d6cd9610004f7d
.reloc 28160 bytes · 13.1% of section data
MD5 b00baf89a8a3463b80fedd5779bc2a9d

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 9bc04ed0a9e568f55932f8a8357fdf62.
  • 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.