GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 973bcad92fb7b30ab5a7a2f35e2eeb24
Latest seen 2025-12-28 23:00:19 (5 months ago)
First seen 2018-01-03 18:06:34 (8 years ago)
Size 105 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-01-03 18:06:34 (8 years ago); latest analysis 2025-12-28 23:00:19 (5 months ago).

Publisher context

Product metadata: SwiftShader 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 SwiftShader libEGL Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2025-12-28 23:00:19 (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: SwiftShader libEGL Dynamic Link Library
MD5: 973bcad92fb7b30ab5a7a2f35e2eeb24
Size: 105 KB
First Published: 2018-01-03 18:06:34 (8 years ago)
Latest Published: 2025-12-28 23:00:19 (5 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-12-28 23:00:19 (5 months ago)
%programfiles%\expertoption
%programfiles%\fast!\nwjs
%appdata%\store\nwjs

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 87.8%
Windows 7 6.1%
Windows 8.1 4.1%
Windows 8 2.0%

The most common operating system signal for libEGL.dll is Windows 10 with 87.8% 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 0x00006974
Image base 0x10000000

PE Sections:

Sections 7
Raw data 106496

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

.text 69120 bytes · 64.9% of section data
MD5 3db9a486d583cc7c35ca913222413b51
.rdata 27136 bytes · 25.5% of section data
MD5 fa3f87a6803f6ba5bbba37bc020c8dd0
.data 2560 bytes · 2.4% of section data
MD5 1676b16ae8c70418b5f1374cc7330f1d
.gfids 512 bytes · 0.5% of section data
Uncommon name
MD5 60d7ebc6aab6f64383b27b0db896c8d3
.tls 512 bytes · 0.5% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 1536 bytes · 1.4% of section data
MD5 38e3680ef066c51ddeb76039b0d5bcf4
.reloc 5120 bytes · 4.8% of section data
MD5 c22b9247a9c89848027d88e2a5778bf3

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 973bcad92fb7b30ab5a7a2f35e2eeb24.
  • 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.