GridinSoft Threat Intelligence

CORE_RL_bzlib_.dll file report

Under review File reputation report
MD5 8e19a8d8559026b49135aca259e1f006
Latest seen 2021-10-12 20:45:59 (4 years ago)
First seen 2017-05-22 11:25:40 (8 years ago)
Size 49 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:25:40 (8 years ago); latest analysis 2021-10-12 20:45:59 (4 years 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 2021-10-12 20:45:59 (4 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: libbzip2 - bzip2 compression library
Company Name: Julian Seward, jseward@acm.org
MD5: 8e19a8d8559026b49135aca259e1f006
Size: 49 KB
First Published: 2017-05-22 11:25:40 (8 years ago)
Latest Published: 2021-10-12 20:45:59 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-10-12 20:45:59 (4 years ago)
%localappdata%\compuclever\ultra file opener
%localappdata%\compuclever

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 65.4%
Windows 7 15.4%
Windows 8.1 11.5%
Windows Vista 3.8%
Windows 8 3.8%

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

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 0x00009ce5
Image base 0x10000000

PE Sections:

Sections 5
Raw data 49664

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

.text 37888 bytes · 76.3% of section data
MD5 d8da2ada8be446d8f56d7333c2ddb4d2
.rdata 5120 bytes · 10.3% of section data
MD5 34f56d2efd90a90626b055cc2a513d64
.data 3584 bytes · 7.2% of section data
MD5 c8f71d25e7232ee4e49c8287619fe9da
.rsrc 2048 bytes · 4.1% of section data
MD5 09732d1d32c041d49125597b403df0b3
.reloc 1024 bytes · 2.1% of section data
MD5 7389d1938cebdbd64b011a113dc9c86d

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 8e19a8d8559026b49135aca259e1f006.
  • 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.