GridinSoft Threat Intelligence

CORE_RL_png_.dll file report

Under review File reputation report
MD5 628743f05c44813bef5ce7c2ea5989d2
Latest seen 2023-12-20 23:50:10 (2 years ago)
First seen 2017-05-22 11:25:42 (9 years ago)
Size 123 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:25:42 (9 years ago); latest analysis 2023-12-20 23:50:10 (2 years ago).

Publisher context

Company metadata: Glenn Randers-Pehrson - randeg@alum.rpi.edu. 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 - randeg@alum.rpi.edu. The current detection status is Undefined, based on the latest analysis from 2023-12-20 23:50:10 (2 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: libpng - PNG file format reference library
Company Name: Glenn Randers-Pehrson - randeg@alum.rpi.edu
MD5: 628743f05c44813bef5ce7c2ea5989d2
Size: 123 KB
First Published: 2017-05-22 11:25:42 (9 years ago)
Latest Published: 2023-12-20 23:50:10 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-20 23:50:10 (2 years ago)
%localappdata%\compuclever\ultra file opener
%localappdata%\compuclever

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 66.7%
Windows 7 14.8%
Windows 8.1 11.1%
Windows Vista 3.7%
Windows 8 3.7%

The most common operating system signal for CORE_RL_png_.dll is Windows 10 with 66.7% 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 0x000184ee
Image base 0x10000000

PE Sections:

Sections 5
Raw data 124928

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

.text 97280 bytes · 77.9% of section data
MD5 54a20a00fd9ea8c1e1d96d203b2eb098
.rdata 22528 bytes · 18.0% of section data
MD5 68ee8cf438eb9f5200cf15a311708246
.data 512 bytes · 0.4% of section data
MD5 f8c93ffe1284f75ed450a1867fda193e
.rsrc 2048 bytes · 1.6% of section data
MD5 7a9da6349f02fd459710096230038153
.reloc 2560 bytes · 2.0% of section data
MD5 0af454f542d0b3b78953f296b1cb8eca

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 628743f05c44813bef5ce7c2ea5989d2.
  • 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.