GridinSoft Threat Intelligence
libEGL.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2023-03-24 23:02:15 (3 years ago); latest analysis 2023-04-18 23:17:52 (3 years ago).
Product metadata: ANGLE libEGL Dynamic Link Library.
Signed by Microsoft Corporation;Microsoft 3rd Party Application Component. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
libEGL.dll is a Windows file recorded in the ThreatInfo database. It is associated with ANGLE libEGL Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2023-04-18 23:17:52 (3 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.
File Details
| Product Name: | ANGLE libEGL Dynamic Link Library |
| MD5: | de34016f5fde8a480a6025ebd5b85f1b |
| Size: | 486 KB |
| First Published: | 2023-03-24 23:02:15 (3 years ago) |
| Latest Published: | 2023-04-18 23:17:52 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2023-04-18 23:17:52 (3 years ago) |
Overview
| Signed By: | Microsoft Corporation;Microsoft 3rd Party Application Component |
| 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.
Common Places:
| %programfiles%\microsoft\edge\application |
| %programfiles%\microsoft\edgewebview\application |
| %programfiles%\microsoft\edgecore |
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.
Geographic signal
Observed country distribution
ThreatInfo has seen libEGL.dll across 20 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 18.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
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.
Analysis
libEGL.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
77d4181c989e576dd2823957610cb054
b3b95a00a0ca7d6be811f8fda0439c51
36714fadc9b128f122c790126a6a76fd
aa21d752a9b3a643bd2a178aad532311
f50da9a366ee05ed7f06d70926bebb8c
bf4434642476300d1f65f7ac8ac7d93c
8ba86516d84cef220ecd4ff8550b6df0
1f354d76203061bfdd5a53dae48d5435
79bf60a93daf03179b6f9ae1dcd371e2
8a92c0a2313bc39349e1d8b1fbc582d7
bbdce8787e6b3f49848e68b1e8c01ad8
4d3d82df424399ac1e425908315f11e7
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.