GridinSoft Threat Intelligence

libGLESv2.dll file report

Under review File reputation report
MD5 1196be50e7f9f56901865c0cfa76ca3e
Latest seen 2025-12-28 23:00:19 (5 months ago)
First seen 2018-01-03 18:06:34 (8 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-01-03 18:06:34 (8 years ago); latest analysis 2025-12-28 23:00:19 (5 months ago).

Publisher context

Product metadata: SwiftShader libGLESv2 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.

libGLESv2.dll is a Windows file recorded in the ThreatInfo database. It is associated with SwiftShader libGLESv2 Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2025-12-28 23:00:19 (5 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: SwiftShader libGLESv2 Dynamic Link Library
MD5: 1196be50e7f9f56901865c0cfa76ca3e
Size: 1 MB
First Published: 2018-01-03 18:06:34 (8 years ago)
Latest Published: 2025-12-28 23:00:19 (5 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-12-28 23:00:19 (5 months ago)
%programfiles%\expertoption
%programfiles%\fast!\nwjs
%appdata%\store\nwjs

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 87.8%
Windows 7 6.1%
Windows 8.1 4.1%
Windows 8 2.0%

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

PE Sections:

Sections 7
Raw data 2012160

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

.text 1689088 bytes · 83.9% of section data
MD5 7f16e8b7db1f69c0041b331f59232397
.rdata 248320 bytes · 12.3% of section data
MD5 db964d9f2ffd14b13c9b07cd0478ed0e
.data 11776 bytes · 0.6% of section data
MD5 638c86262649747815013f0eb0638ca2
.tls 512 bytes · 0.0% of section data
MD5 adb00c88d5919bab3c4b160cbf2abed5
.gfids 3584 bytes · 0.2% of section data
Uncommon name
MD5 493dede53d0cbe9821636ab8166f7875
.rsrc 1024 bytes · 0.1% of section data
MD5 bea92f4015fe2a87b5116b83892a550b
.reloc 57856 bytes · 2.9% of section data
MD5 3772cb657f0af9af803c9262b2d5a156

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 1196be50e7f9f56901865c0cfa76ca3e.
  • 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.