GridinSoft Threat Intelligence

zlib1.dll file report

Under review File reputation report
MD5 bcaf983ab27437913e76776f79b850c5
Latest seen 2023-01-30 23:39:02 (3 years ago)
First seen 2017-05-25 16:09:53 (8 years ago)
Size 98 KB
Product zlib

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-25 16:09:53 (8 years ago); latest analysis 2023-01-30 23:39:02 (3 years ago).

Publisher context

Product metadata: zlib.

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.

zlib1.dll is a Windows file recorded in the ThreatInfo database. It is associated with zlib. The current detection status is Undefined, based on the latest analysis from 2023-01-30 23:39:02 (3 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: zlib
MD5: bcaf983ab27437913e76776f79b850c5
Size: 98 KB
First Published: 2017-05-25 16:09:53 (8 years ago)
Latest Published: 2023-01-30 23:39:02 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-01-30 23:39:02 (3 years ago)
%programfiles%\pcdapp
%programfiles%\pcdata
%localappdata%\math problem solver\cpu
%appdata%
%system%\dfrg
%appdata%\microsoft\sys32
%appdata%\miner
%windir%\init\spoolv32
%programfiles%
%system%

ThreatInfo has observed zlib1.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 7 68.4%
Windows 10 8.8%
Windows Vista 8.8%
Windows XP 8.8%
Windows 8 3.5%
Windows 8.1 1.8%

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

zlib1.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x000010c0
Image base 0x62e80000

PE Sections:

Sections 8
Raw data 99840

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

.text 74752 bytes · 74.9% of section data
MD5 d23f1394083513c1cf5ad07548f4a37b
.data 512 bytes · 0.5% of section data
MD5 b43b0b6e3c566c7d3fec5a5da02124ab
.rdata 18944 bytes · 19.0% of section data
MD5 88665344860e975486606a90a2d9d82d
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 2048 bytes · 2.1% of section data
MD5 6c24b4c01f338130da86bc3c9fd2184f
.idata 1024 bytes · 1.0% of section data
MD5 4432591142f455992726b4ea50d29ebe
.rsrc 1024 bytes · 1.0% of section data
MD5 01678a5500f0eadbe52403e7b3447f4e
.reloc 1536 bytes · 1.5% of section data
MD5 74ffe253cdedfe56b7e51dd2b5be0202

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