GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 c069182dee9678bf9dbb7cd820aa1b1c
Latest seen 2024-05-10 23:05:57 (2 years ago)
First seen 2017-05-22 10:20:40 (9 years ago)
Size 73 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 10:20:40 (9 years ago); latest analysis 2024-05-10 23:05:57 (2 years ago).

Publisher context

Product metadata: ANGLE 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 ANGLE libEGL Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2024-05-10 23:05:57 (2 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: ANGLE libEGL Dynamic Link Library
MD5: c069182dee9678bf9dbb7cd820aa1b1c
Size: 73 KB
First Published: 2017-05-22 10:20:40 (9 years ago)
Latest Published: 2024-05-10 23:05:57 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-10 23:05:57 (2 years ago)
%commonappdata%\ubar\ubar\v1.8.0.6
%programfiles%\flip shopping catalog
%commonappdata%\ubar\ubar\modules\cef
%commonappdata%\ubar\backup\ubar\modules\cef
%commonappdata%\ubar\backup\ubar\v1.7.2.4
%commonappdata%\ubar\ubar\v1.7.2.4
%commonappdata%\ubar\ubar\v1.7.1.2
%commonappdata%\ubar\backup\ubar\modules
%commonappdata%\ubar\ubar\modules
%commonappdata%\ubar\ubar

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 67.2%
Windows 7 22.6%
Windows 8.1 9.0%
Windows 8 1.1%

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

PE Sections:

Sections 5
Raw data 74240

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

.text 42496 bytes · 57.2% of section data
MD5 f5e6aacf418ba00e98d1625a100eaea7
.rdata 22016 bytes · 29.7% of section data
MD5 7560b9515a381ae4a80db4e22d2d69d5
.data 4608 bytes · 6.2% of section data
MD5 c62da837d12e11628d2191f1b4c3d5bb
.rsrc 1536 bytes · 2.1% of section data
MD5 52e1d339243a9ffaf158506a07859c00
.reloc 3584 bytes · 4.8% of section data
MD5 ac8f9a8856c51cd71c5832b29fcf99e3

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