GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 77f65a7b8de5b74b0ad5dd19c9905c9d
Latest seen 2025-12-22 23:02:13 (5 months ago)
First seen 2020-07-25 15:13:54 (5 years ago)
Size 21 KB
Product libEGL
Signed by The Qt Company Oy

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-25 15:13:54 (5 years ago); latest analysis 2025-12-22 23:02:13 (5 months ago).

Publisher context

Product metadata: libEGL.

Digital signature

Signed by The Qt Company Oy. 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 2025-12-22 23:02:13 (5 months 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: 77f65a7b8de5b74b0ad5dd19c9905c9d
Size: 21 KB
First Published: 2020-07-25 15:13:54 (5 years ago)
Latest Published: 2025-12-22 23:02:13 (5 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-12-22 23:02:13 (5 months ago)
Signed By: The Qt Company Oy
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.

%commonappdata%
%programfiles%

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 82.7%
Windows 7 12.3%
Windows 8 2.5%
Windows Embedded Standard 1.2%
Windows 8.1 1.2%

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

libEGL.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 0x000017a6
Image base 0x10000000

PE Sections:

Sections 5
Raw data 14848

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

.text 4608 bytes · 31.0% of section data
MD5 6a7b6a378669da3c68e06ac1ca575bb7
.rdata 7680 bytes · 51.7% of section data
MD5 4b5db13f230186e6962516b1edafc757
.data 512 bytes · 3.4% of section data
MD5 bfcdd9374007569a72a55e928d02fa3f
.rsrc 1536 bytes · 10.3% of section data
MD5 9cc98d5892298e8301f746da6c8af5d2
.reloc 512 bytes · 3.4% of section data
MD5 678f9bc2bbe42d2ce1e5ba43fc566bc3

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 77f65a7b8de5b74b0ad5dd19c9905c9d.
  • 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.