GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 9ca3973c883b10bb8e5379c4cd47a1b8
Latest seen 2024-10-09 23:00:50 (2 years ago)
First seen 2017-06-24 02:08:56 (8 years ago)
Size 100 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-24 02:08:56 (8 years ago); latest analysis 2024-10-09 23:00:50 (2 years ago).

Publisher context

Product metadata: ANGLE libEGL Dynamic Link 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.

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 2024-10-09 23:00:50 (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: ANGLE libEGL Dynamic Link Library
MD5: 9ca3973c883b10bb8e5379c4cd47a1b8
Size: 100 KB
First Published: 2017-06-24 02:08:56 (8 years ago)
Latest Published: 2024-10-09 23:00:50 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-09 23:00:50 (2 years ago)
%appdata%\windows
%windir%\inf\netlibrariestip\0009\v3.5.56385\1049
%localappdata%\google
%system%\config\systemprofile\appdata\local\google
%commonappdata%
%commonappdata%\system32
%commonappdata%\windows
%appdata%
%commonappdata%\microsoft\drm

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 56.7%
Windows 7 35.0%
Windows 8.1 5.0%
Windows Server 2012 R2 2.5%
Windows Server 2008 R2 0.8%

The most common operating system signal for libEGL.dll is Windows 10 with 56.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 CUI. 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 CUI
Entry point 0x00009f31
Image base 0x10000000

PE Sections:

Sections 5
Raw data 101376

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

.text 67584 bytes · 66.7% of section data
MD5 1b4eebb109789915a61673bde3b105dd
.rdata 21504 bytes · 21.2% of section data
MD5 4a5a784030004c1cdc4413c9b986e502
.data 4096 bytes · 4.0% of section data
MD5 3a429fe3d11f8116a472bde8b6fc4892
.rsrc 1024 bytes · 1.0% of section data
MD5 668b7341f79f91cf5c016dc133b41fe7
.reloc 7168 bytes · 7.1% of section data
MD5 210c6ada0c51c12e20d835b95280c96e

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 9ca3973c883b10bb8e5379c4cd47a1b8.
  • 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.