GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 b5e5042f390013b7265f8642e95e4167
Latest seen 2021-01-04 04:32:11 (5 years ago)
First seen 2021-01-04 04:32:11 (5 years ago)
Size 401 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-04 04:32:11 (5 years ago); latest analysis 2021-01-04 04:32:11 (5 years 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 2021-01-04 04:32:11 (5 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: SwiftShader libEGL Dynamic Link Library
MD5: b5e5042f390013b7265f8642e95e4167
Size: 401 KB
First Published: 2021-01-04 04:32:11 (5 years ago)
Latest Published: 2021-01-04 04:32:11 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-04 04:32:11 (5 years ago)
%localappdata%\webnavigatorbrowser\application\2.2.1.7

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 100.0%

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.

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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x000220e8
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 410112

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

.text 286208 bytes · 69.8% of section data
MD5 3c222a5e5769a8aa0e32107faf506db6
.rdata 92672 bytes · 22.6% of section data
MD5 25e91b3d8ac6121ae7ba128136eb9e94
.data 8192 bytes · 2.0% of section data
MD5 c9c5b38023466ad3b1db75216f37ee81
.pdata 15872 bytes · 3.9% of section data
MD5 9f5a352dd995dd605a3b3f8b2605c28a
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 50ecd075a66d3c31d6cc1a34fa4a75b3
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.1% of section data
Uncommon name
MD5 bb4983b4abfc76274fbcbb4c1d30dbe9
.rsrc 1536 bytes · 0.4% of section data
MD5 9c3d1178125ddb44e64edc2daf48af82
.reloc 4096 bytes · 1.0% of section data
MD5 c8ceba53a535ad08732c84d8022be8fd

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 b5e5042f390013b7265f8642e95e4167.
  • 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.