GridinSoft Threat Intelligence

libGLESv2.dll file report

Under review File reputation report
MD5 49ad4ace0c612f97c09a49bae9b098f0
Latest seen 2026-02-08 23:06:24 (3 months ago)
First seen 2021-06-19 20:27:21 (4 years ago)
Size 5 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-06-19 20:27:21 (4 years ago); latest analysis 2026-02-08 23:06:24 (3 months 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.

libGLESv2.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 2026-02-08 23:06:24 (3 months 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: 49ad4ace0c612f97c09a49bae9b098f0
Size: 5 MB
First Published: 2021-06-19 20:27:21 (4 years ago)
Latest Published: 2026-02-08 23:06:24 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-08 23:06:24 (3 months ago)
%appdata%\drpsu
%sysdrive%\windows.old\users\joão marcelo\appdata\roaming\drpsu
%profile%\abio\dati applicazioni\drpsu

ThreatInfo has observed libGLESv2.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 79.9%
Windows 7 16.1%
Windows 8.1 2.3%
Windows Server 2012 R2 0.6%
Windows 8 0.6%
Windows XP 0.6%

The most common operating system signal for libGLESv2.dll is Windows 10 with 79.9% 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.

libGLESv2.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 0x0039f2f0
Image base 0x10000000

PE Sections:

Sections 8
Raw data 5693952

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

.text 3961856 bytes · 69.6% of section data
MD5 9432b57f706eea19a6eff35f2bb059b6
.rdata 1367040 bytes · 24.0% of section data
MD5 253f1cc973cfbbbb080765e20b5d2515
.data 148480 bytes · 2.6% of section data
MD5 f63aae253a0346415abfa71ebf62e031
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 5f67ac73480815f67fb1af6a38ad45f4
.tls 512 bytes · 0.0% of section data
MD5 134b5956ca7a32f7432044b77c8438ef
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 9c85a976937ca7885ec159500bc435df
.rsrc 1536 bytes · 0.0% of section data
MD5 6409a5c2e3241248dd0fa160527aaa98
.reloc 213504 bytes · 3.7% of section data
MD5 c5bd7d58616f705e8928c6e9cfabaeef

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 49ad4ace0c612f97c09a49bae9b098f0.
  • 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.