GridinSoft Threat Intelligence

CORE_RL_png_.dll file report

Under review File reputation report
MD5 72a09ccbebc1645c5e3a80692640689a
Latest seen 2025-04-05 23:02:04 (a year ago)
First seen 2025-04-05 23:02:04 (a year ago)
Size 159 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Company metadata: Glenn Randers-Pehrson - glennrp@users.sf.net. Product metadata: libpng - PNG file format reference 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_png_.dll is a Windows file recorded in the ThreatInfo database. It is associated with libpng - PNG file format reference library. The reported company name is Glenn Randers-Pehrson - glennrp@users.sf.net. The current detection status is Undefined, based on the latest analysis from 2025-04-05 23:02:04 (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: libpng - PNG file format reference library
Company Name: Glenn Randers-Pehrson - glennrp@users.sf.net
MD5: 72a09ccbebc1645c5e3a80692640689a
Size: 159 KB
First Published: 2025-04-05 23:02:04 (a year ago)
Latest Published: 2025-04-05 23:02:04 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-05 23:02:04 (a year ago)
%appdata%\hudun\compressmagician\resources\app\bin

ThreatInfo has observed CORE_RL_png_.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_png_.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_png_.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 0x0001f678
Image base 0x10000000

PE Sections:

Sections 6
Raw data 162304

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

.text 127488 bytes · 78.5% of section data
MD5 8c133229c03ec40457f5d5605962103c
.rdata 28160 bytes · 17.4% of section data
MD5 5aa8245ae11dfa556371ced60c8ee443
.data 512 bytes · 0.3% of section data
MD5 e288e4c0423c7e1a6e2f9bfd093c56a8
.gfids 512 bytes · 0.3% of section data
Uncommon name
MD5 0beca58bd2dadf04edcdef931688f0f8
.rsrc 2048 bytes · 1.3% of section data
MD5 535fc1812de784c4f9c291d014721684
.reloc 3584 bytes · 2.2% of section data
MD5 12b1717971b9dbb324294862b7b4f10d

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 72a09ccbebc1645c5e3a80692640689a.
  • 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.