GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 c78ad4c9fdd77e87ab9253b4b3841a1b
Latest seen 2023-09-12 23:45:44 (2 years ago)
First seen 2023-09-12 23:45:44 (2 years ago)
Size 35 KB
Product libEGL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-09-12 23:45:44 (2 years ago); latest analysis 2023-09-12 23:45:44 (2 years ago).

Publisher context

Product metadata: libEGL.

Digital signature

Signed by Adoreshare Co.,Limited. 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.

libEGL.dll is a Windows file recorded in the ThreatInfo database. It is associated with libEGL. The current detection status is Undefined, based on the latest analysis from 2023-09-12 23:45:44 (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: libEGL
MD5: c78ad4c9fdd77e87ab9253b4b3841a1b
Size: 35 KB
First Published: 2023-09-12 23:45:44 (2 years ago)
Latest Published: 2023-09-12 23:45:44 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-09-12 23:45:44 (2 years ago)
Signed By: Adoreshare Co.,Limited
Status: Valid

The signature on libEGL.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%\hitpaw video editor

ThreatInfo has observed libEGL.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 libEGL.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.

libEGL.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 0x00001788
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 16896

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

.text 4608 bytes · 27.3% of section data
MD5 42f685243c4c23553c7882574035555d
.rdata 9216 bytes · 54.5% of section data
MD5 33c0d17d886bb49129ae061e365db244
.data 512 bytes · 3.0% of section data
MD5 3e54b380c18e9fb1c3756c3724029e08
.pdata 512 bytes · 3.0% of section data
MD5 d00151c2f169747b3cb79c767ae6b2f2
.rsrc 1536 bytes · 9.1% of section data
MD5 8bc260ce1bfb8e8ca2af64f61f50affb
.reloc 512 bytes · 3.0% of section data
MD5 f721538bb595468b40570dc1a47598a9

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 c78ad4c9fdd77e87ab9253b4b3841a1b.
  • 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.