GridinSoft Threat Intelligence

libGLESV2.dll file report

Under review File reputation report
MD5 131f9b3cfbdbf0abdf83842cb5fdeb4f
Latest seen 2022-06-24 23:18:46 (3 years ago)
First seen 2020-07-02 19:22:11 (5 years ago)
Size 4 MB
Product libGLESv2

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-02 19:22:11 (5 years ago); latest analysis 2022-06-24 23:18:46 (3 years ago).

Publisher context

Product metadata: libGLESv2.

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 libGLESv2. The current detection status is Undefined, based on the latest analysis from 2022-06-24 23:18:46 (3 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: libGLESv2
MD5: 131f9b3cfbdbf0abdf83842cb5fdeb4f
Size: 4 MB
First Published: 2020-07-02 19:22:11 (5 years ago)
Latest Published: 2022-06-24 23:18:46 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-06-24 23:18:46 (3 years ago)
%programfiles%

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 7 75.0%
Windows 10 25.0%

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

libGLESV2.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00001380
Image base 0x66a80000

PE Sections:

Sections 11
Raw data 4506112

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

.text 3264000 bytes · 72.4% of section data
MD5 30f83616e4dfeab84e6e2619087485f0
.data 5632 bytes · 0.1% of section data
MD5 b4b133350b9c1f4f0246b69f41afe7d3
.rdata 506880 bytes · 11.2% of section data
MD5 3e7c9e664721309636014e08eeca68d4
.eh_fram 594944 bytes · 13.2% of section data
Uncommon name
MD5 4ca76d3914605bb83993546623295c7a
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 24064 bytes · 0.5% of section data
MD5 879aa3d69c95082a06e5ce79c934c6a9
.idata 10240 bytes · 0.2% of section data
MD5 cf71039ca87e55ce6f3959f7784fdb4e
.CRT 512 bytes · 0.0% of section data
MD5 d1d0b123a010d99cfc52bd9e5446b433
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 0.0% of section data
MD5 20785559461a5386036329116428d45c
.reloc 98304 bytes · 2.2% of section data
MD5 310e8528757adf468631de86a2db4322

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 131f9b3cfbdbf0abdf83842cb5fdeb4f.
  • 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.