GridinSoft Threat Intelligence

libegl.dll file report

Under review File reputation report
MD5 17e84b364c6556b9a55f38e1f57895b6
Latest seen 2022-08-03 23:48:55 (3 years ago)
First seen 2020-11-13 04:03:52 (5 years ago)
Size 326 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-11-13 04:03:52 (5 years ago); latest analysis 2022-08-03 23:48:55 (3 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 2022-08-03 23:48:55 (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.

Product Name: SwiftShader libEGL Dynamic Link Library
MD5: 17e84b364c6556b9a55f38e1f57895b6
Size: 326 KB
First Published: 2020-11-13 04:03:52 (5 years ago)
Latest Published: 2022-08-03 23:48:55 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-03 23:48:55 (3 years ago)
%localappdata%\orbitum\application\80.0.3987.123

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 66.7%
Windows 7 33.3%

The most common operating system signal for libegl.dll is Windows 10 with 66.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 0x0001e3b9
Image base 0x10000000

PE Sections:

Sections 8
Raw data 332800

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

.text 249856 bytes · 75.1% of section data
MD5 1168615126450042e477e9a3862a644c
.rdata 59392 bytes · 17.8% of section data
MD5 583688864ca7e324a245678f2ff7ba3f
.data 7168 bytes · 2.2% of section data
MD5 e4adf3b476fc63927e2ae5b3fd2ba5a1
.00cfg 512 bytes · 0.2% of section data
Uncommon name
MD5 6c2ae5bb2920a45f271e941900f62cfa
.tls 512 bytes · 0.2% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.voltbl 512 bytes · 0.2% of section data
Uncommon name
MD5 6a17b8c19bd020c4fd7c9c245d155837
.rsrc 1536 bytes · 0.5% of section data
MD5 5e5541d6a4e11b02d494d857de2e9599
.reloc 13312 bytes · 4.0% of section data
MD5 e7dd407fb0fbf297fae1dd86a2e0a9df

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 17e84b364c6556b9a55f38e1f57895b6.
  • 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.