GridinSoft Threat Intelligence
libglesv2.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-21 14:10:01 (9 years ago); latest analysis 2021-01-13 03:58:07 (5 years ago).
Product metadata: ANGLE libGLESv2 Dynamic Link Library.
Signed by Google Inc. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
libglesv2.dll is a Windows file recorded in the ThreatInfo database. It is associated with ANGLE libGLESv2 Dynamic Link Library. The current detection status is Clean, based on the latest analysis from 2021-01-13 03:58:07 (5 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | ANGLE libGLESv2 Dynamic Link Library |
| MD5: | 4f70ab082c2a5f950afa913b8d517ad3 |
| Size: | 1 MB |
| First Published: | 2017-05-21 14:10:01 (9 years ago) |
| Latest Published: | 2021-01-13 03:58:07 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-13 03:58:07 (5 years ago) |
Overview
| Signed By: | Google Inc |
| Status: | Valid |
The signature on libglesv2.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %programfiles%\bigmay\application |
| %programfiles%\shutness\application |
| %programfiles%\mapbob\application |
| %programfiles%\ontoe\application |
| %programfiles%\zooarm\application |
| %programfiles%\baghair\application |
| %programfiles%\bangkiss\application |
| %programfiles%\bemike\application |
| %programfiles%\nosekiss\application |
| %programfiles%\inper\application |
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.
Geographic signal
Observed country distribution
ThreatInfo has seen libglesv2.dll across 24 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Vietnam with 16.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for libglesv2.dll is Windows 7 with 44.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.
Analysis
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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d4399a7dd91d2bb5682f7be1df536c68
ff9d84dc461579b3dad66f5a9836d481
069fb65a6e606167181e7d06038fcf9e
0c955808e36640eb40febf0806c7b1e3
3cfb954856ab7c5547b64b754d8f56f4
ca23983d1564b6030d1a0506901da2ba
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.