GridinSoft Threat Intelligence

CORE_RL_bzlib_.dll file report

Under review File reputation report
MD5 0e675a48c5732c3ab82d9822cc4cc668
Latest seen 2025-04-05 23:01:55 (a year ago)
First seen 2025-04-05 23:01:55 (a year ago)
Size 60 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Company metadata: Julian Seward, jseward@acm.org. Product metadata: libbzip2 - bzip2 compression library.

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.

CORE_RL_bzlib_.dll is a Windows file recorded in the ThreatInfo database. It is associated with libbzip2 - bzip2 compression library. The reported company name is Julian Seward, jseward@acm.org. The current detection status is Undefined, based on the latest analysis from 2025-04-05 23:01:55 (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: libbzip2 - bzip2 compression library
Company Name: Julian Seward, jseward@acm.org
MD5: 0e675a48c5732c3ab82d9822cc4cc668
Size: 60 KB
First Published: 2025-04-05 23:01:55 (a year ago)
Latest Published: 2025-04-05 23:01:55 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-05 23:01:55 (a year ago)
%appdata%\hudun\compressmagician\resources\app\bin

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

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

CORE_RL_bzlib_.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 0x0000bdae
Image base 0x10000000

PE Sections:

Sections 6
Raw data 60928

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

.text 47616 bytes · 78.2% of section data
MD5 0c5d9f72006f19b7fe78cd01dd891165
.rdata 6144 bytes · 10.1% of section data
MD5 01f4f5bfc7f57d1f03e07072f05e9bda
.data 3584 bytes · 5.9% of section data
MD5 f4e48b00e9bcba248cd99df6f6a5024f
.gfids 512 bytes · 0.8% of section data
Uncommon name
MD5 0beca58bd2dadf04edcdef931688f0f8
.rsrc 2048 bytes · 3.4% of section data
MD5 25127c24a7fb2361ab16c0ab99b5b1b9
.reloc 1024 bytes · 1.7% of section data
MD5 6080d2c6f5d89a924e36e1064af42339

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 0e675a48c5732c3ab82d9822cc4cc668.
  • 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.