libegl.dll file report

MD5 2fbf54b95d1e6bc7e687a29263acd02e
Latest seen 2025-03-16 23:04:07 (a year ago)
First seen 2017-05-21 05:04:43 (8 years ago)
Size 85 KB
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 05:04:43 (8 years ago); latest analysis 2025-03-16 23:04:07 (a year ago).

Publisher context

Product metadata: ANGLE libEGL Dynamic Link Library.

Digital signature

Signed by Google Inc. 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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

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 Clean, based on the latest analysis from 2025-03-16 23:04:07 (a year ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: ANGLE libEGL Dynamic Link Library
MD5: 2fbf54b95d1e6bc7e687a29263acd02e
Size: 85 KB
First Published: 2017-05-21 05:04:43 (8 years ago)
Latest Published: 2025-03-16 23:04:07 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-03-16 23:04:07 (a year ago)
Signed By: Google Inc
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%\zoohair\application
%programfiles%\canrain\application
%programfiles%\dayglad\application
%programfiles%\footjane\application
%programfiles%\bookness\application
%programfiles%\dopig\application
%programfiles%\bagsarah\application
%programfiles%\eggper\application
%programfiles%\hotleaf\application
%programfiles%\cupduck\application

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.

15.9%
13.5%
12.5%
6.9%
6.8%
6.3%
6.0%
5.0%
2.7%
2.4%
1.3%
1.1%
1.0%
1.0%
0.8%
0.8%
0.7%
0.7%
0.7%
0.7%
0.7%
0.6%
0.6%
0.6%
0.6%
0.5%
0.5%
0.5%
0.5%
0.5%
0.4%
0.4%
0.4%
0.3%
0.3%
0.3%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%

The strongest geographic signal for this file is Vietnam with 15.9% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 49.3%
Windows 7 41.7%
Windows 8.1 6.8%
Windows 8 2.1%
Windows Server 2012 R2 0.1%

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

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x00001760

PE Sections:

Name Size of data MD5
.text 43520 6f81270ec343aa810f26a1cd1e788c6d
.rdata 28160 17a93ec69a6f95d14392824ade9dd946
.data 2048 f9142dd41bddc6af733f7ead05e80a9a
.rsrc 1536 c9ad9c5f60a1253c2fee7c6024212fe7
.reloc 4096 9fb9afef4e0bcb1216385991ba64db66

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.

More information: