GridinSoft Threat Intelligence

bz2.dll file report

Under review File reputation report
MD5 61b8ccdd371dc0153830817fd84e9b99
Latest seen 2025-04-12 23:01:50 (a year ago)
First seen 2025-04-12 23:01:50 (a year ago)
Size 85 KB
Publisher BZ
Product bz2

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-04-12 23:01:50 (a year ago); latest analysis 2025-04-12 23:01:50 (a year ago).

Publisher context

Company metadata: BZ. Product metadata: bz2.

Digital signature

Signed by Beijing iQIYI Science & Technology Co., Ltd.. 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.

bz2.dll is a Windows file recorded in the ThreatInfo database. It is associated with bz2. The reported company name is BZ. The current detection status is Undefined, based on the latest analysis from 2025-04-12 23:01:50 (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.

Product Name: bz2
Company Name: BZ
MD5: 61b8ccdd371dc0153830817fd84e9b99
Size: 85 KB
First Published: 2025-04-12 23:01:50 (a year ago)
Latest Published: 2025-04-12 23:01:50 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-12 23:01:50 (a year ago)

The signature on bz2.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%\iqiyi video\lstyle

ThreatInfo has observed bz2.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 100.0%

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

bz2.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0000ed30
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 75776

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

.text 59392 bytes · 78.4% of section data
MD5 c54be28396cadd7497079576b8977614
.rdata 9216 bytes · 12.2% of section data
MD5 9719e4c8a6f986881e9fdb09c1f01776
.data 3584 bytes · 4.7% of section data
MD5 6873342f11859da79876e6a5f343b07a
.pdata 2048 bytes · 2.7% of section data
MD5 cb5c56d051ced639315546b26a219978
.rsrc 1024 bytes · 1.4% of section data
MD5 81b193dc799fbe3671049d3d95fc2055
.reloc 512 bytes · 0.7% of section data
MD5 e3a6568fbb514b1eb67b50130e183592

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 61b8ccdd371dc0153830817fd84e9b99.
  • 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.