GridinSoft Threat Intelligence

libEGL.dll file report

Under review File reputation report
MD5 620ee84d52013d230356272272939f8d
Latest seen 2021-04-13 20:55:13 (5 years ago)
First seen 2021-04-13 20:55:13 (5 years ago)
Size 320 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-04-13 20:55:13 (5 years ago); latest analysis 2021-04-13 20:55:13 (5 years 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. 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 DriverPack Cloud. The reported company name is DriverPack Solution. The current detection status is Undefined, based on the latest analysis from 2021-04-13 20:55:13 (5 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: DriverPack Cloud
Company Name: DriverPack Solution
MD5: 620ee84d52013d230356272272939f8d
Size: 320 KB
First Published: 2021-04-13 20:55:13 (5 years ago)
Latest Published: 2021-04-13 20:55:13 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-04-13 20:55:13 (5 years ago)
%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.

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 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 0x0001abf0
Image base 0x10000000

PE Sections:

Sections 8
Raw data 327168

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

.text 241664 bytes · 73.9% of section data
MD5 321cdf149502784a1b575634ecd845c5
.rdata 62464 bytes · 19.1% of section data
MD5 86c2d1239d8b8158c6817fd03deeb0fb
.data 7168 bytes · 2.2% of section data
MD5 23614791e63b392ea4d762606ad259c0
.00cfg 512 bytes · 0.2% of section data
Uncommon name
MD5 a274b53dcea2486b5930c6465bb188b7
.tls 512 bytes · 0.2% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.voltbl 512 bytes · 0.2% of section data
Uncommon name
MD5 199ed2412064c711536cee5d3ed2a217
.rsrc 1536 bytes · 0.5% of section data
MD5 01f75df3df1c44758f6d1dd608ecad9d
.reloc 12800 bytes · 3.9% of section data
MD5 be5608d7bb967010a83a3b991af6e374

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 620ee84d52013d230356272272939f8d.
  • 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.