GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 f262780431f943faa8827b024d06f4a8
Latest seen 2022-08-20 23:23:58 (3 years ago)
First seen 2021-11-23 21:22:13 (4 years ago)
Size 454 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-11-23 21:22:13 (4 years ago); latest analysis 2022-08-20 23:23:58 (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-20 23:23:58 (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: f262780431f943faa8827b024d06f4a8
Size: 454 KB
First Published: 2021-11-23 21:22:13 (4 years ago)
Latest Published: 2022-08-20 23:23:58 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-20 23:23:58 (3 years ago)
%localappdata%\programs\kryptex-app

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 0x0002d658
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 464384

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

.text 333312 bytes · 71.8% of section data
MD5 2a0652e4c067a102f399525ce1b9a85f
.rdata 99328 bytes · 21.4% of section data
MD5 a1e5c4a582c3edc5a74fb27c66a04ae7
.data 8192 bytes · 1.8% of section data
MD5 4e74aa6a1a079b3468949de985dea7b1
.pdata 16384 bytes · 3.5% of section data
MD5 faec4198f42bf1a14d33b2c6587df340
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 f6cab3ea6d204511bffd5a337400a0b5
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.1% of section data
Uncommon name
MD5 41e17ddc384cee9592343b7b3657867e
.rsrc 1536 bytes · 0.3% of section data
MD5 ba40bc5f50e29b8f5456109f78faf6af
.reloc 4096 bytes · 0.9% of section data
MD5 16f9b95d92a0fc2fe4693aeca4f1c5e6

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