GridinSoft Threat Intelligence
zlib1.dl1 file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-09-18 08:02:50 (8 years ago); latest analysis 2025-05-26 23:01:25 (a year ago).
Product metadata: zlib.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
zlib1.dl1 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 2025-05-26 23:01:25 (a year 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.
File Details
| Product Name: | zlib |
| MD5: | cb0577e362e193cad14c3d23c40c30d4 |
| Size: | 113 KB |
| First Published: | 2017-09-18 08:02:50 (8 years ago) |
| Latest Published: | 2025-05-26 23:01:25 (a year ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-05-26 23:01:25 (a year ago) |
Common Places:
| %windir%\fonts |
| %windir% |
| %temp% |
| %appdata%\electroneum |
| %sysdrive%\docume~1\bagian~1\locals~1\temp |
| %sysdrive%\appdata\local\temp |
| %appdata% |
| %sysdrive%\docume~1\admini~1\locals~1\temp |
| %sysdrive%\docume~1\master~1\locals~1\temp |
| %sysdrive%\docume~1\admin\locals~1\temp |
ThreatInfo has observed zlib1.dl1 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.
File Names:
2 observed namesThis hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geographic signal
Observed country distribution
ThreatInfo has seen zlib1.dl1 across 36 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Taiwan with 49.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for zlib1.dl1 is Windows 10 with 63.9% 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.
Analysis
zlib1.dl1 is identified as pe for 64-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
4050e74e37ca89d2eae934df8e94de29
398dd74ccc586b8df9141d5fa13c8efb
5ea7f35187568c739609d765fea002cd
0eaab62d5034340ba9e3bbf76d1d3714
2cc5ccef0c66faf4ce88a24bce71b8c1
00000000000000000000000000000000
3e26f6538c9c0d74288a1d56e39f6d59
36f789b801fade124643bcf935099808
b0817a17b10ecd3b4b1016e41948e596
03e9b83bf584522206030930d92ab81d
8408e0e2e09581b4ae4ef4da130f10a0
3775127ac7b075be5b5a41b20247ad08
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.