libEGL.dll threat report

MD5 e24b48ab86d13944753b12758cf63a8b
Latest seen 2025-03-22 23:01:29 (a year ago)
First seen 2020-05-03 20:00:44 (6 years ago)
Size 77 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.DriverPack. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
PUP.DriverPack
Recommended action
Scan and remove
Last analysis
2025-03-22 23:01:29 (a year ago)
File hash
e24b48ab86d13944753b12758cf63a8b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.DriverPack.

Timeline

First seen 2020-05-03 20:00:44 (6 years ago); latest analysis 2025-03-22 23:01:29 (a year ago).

Publisher context

Company metadata: DriverPack Solution. Product metadata: DriverPack Cloud.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

libEGL.dll is a Windows file recorded in the ThreatInfo database. It is associated with DriverPack Cloud. The reported company name is DriverPack Solution. The current detection status is PUP.DriverPack, based on the latest analysis from 2025-03-22 23:01:29 (a year ago).

If libEGL.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as PUP.DriverPack.

Product Name: DriverPack Cloud
Company Name: DriverPack Solution
MD5: e24b48ab86d13944753b12758cf63a8b
Size: 77 KB
First Published: 2020-05-03 20:00:44 (6 years ago)
Latest Published: 2025-03-22 23:01:29 (a year ago)
Status: PUP.DriverPack (on last analysis)
Analysis Date: 2025-03-22 23:01:29 (a year ago)
libEGL.dll detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu
%appdata%\drpsu

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.

29.4%
11.8%
11.8%
5.9%
5.9%
5.9%
5.9%
5.9%
5.9%
5.9%
5.9%

The strongest geographic signal for this file is Turkey with 29.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 55.0%
Windows 10 45.0%

The most common operating system signal for libEGL.dll is Windows 7 with 55.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 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x000015ce

PE Sections:

Name Size of data MD5
.text 42496 410da70f6d0a4b7e88cece924ea7bf8f
.rdata 28160 1d97e96a8e3b40e6f7d5179b8f0797b4
.data 2048 b6e9a5be6b3f819bb478d3e4a94b4392
.gfids 512 934142e2505738e4e0b711635f0447f5
.rsrc 1024 3c415b58490570298f0d405e7d6ad416
.reloc 4096 c14067d65b3e518cc2ba36df7e159c72

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.

More information: