GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 44741358493014223475cbcd0a074837
Latest seen 2022-06-24 23:20:58 (3 years ago)
First seen 2020-07-02 19:20:13 (5 years ago)
Size 23 KB
Product libEGL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-02 19:20:13 (5 years ago); latest analysis 2022-06-24 23:20:58 (3 years ago).

Publisher context

Product metadata: libEGL.

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 libEGL. The current detection status is Undefined, based on the latest analysis from 2022-06-24 23:20: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: libEGL
MD5: 44741358493014223475cbcd0a074837
Size: 23 KB
First Published: 2020-07-02 19:20:13 (5 years ago)
Latest Published: 2022-06-24 23:20:58 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-06-24 23:20:58 (3 years ago)
%programfiles%

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 7 75.0%
Windows 10 25.0%

The most common operating system signal for libEGL.dll is Windows 7 with 75.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 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00001380
Image base 0x66e00000

PE Sections:

Sections 11
Raw data 22528

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

.text 6656 bytes · 29.5% of section data
MD5 107dae70718b8fd03a1147d779400c0c
.data 512 bytes · 2.3% of section data
MD5 332eca74d17e1cc45bf1aa8e96f230d0
.rdata 512 bytes · 2.3% of section data
MD5 877c1c06b00e72771e8beb3cff41c0da
.eh_fram 4096 bytes · 18.2% of section data
Uncommon name
MD5 ff036300eae3773e4a4b933b42b54bf6
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 2560 bytes · 11.4% of section data
MD5 393de1ed0a4e4cd1eb6612edfc48202e
.idata 5120 bytes · 22.7% of section data
MD5 445fbb30690fbea8047b27acfebcd4d1
.CRT 512 bytes · 2.3% of section data
MD5 26d39424695c818727c94777d637c602
.tls 512 bytes · 2.3% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 4.5% of section data
MD5 3eb9a04e55cdcdac121b2f2fedde3806
.reloc 1024 bytes · 4.5% of section data
MD5 d223415b2cb7f8d5baab2ad3954fb9f4

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 44741358493014223475cbcd0a074837.
  • 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.