GridinSoft Threat Intelligence

libglesv2.dll file report

Under review File reputation report
MD5 2899808f52af4c068852f8328bc29716
Latest seen 2022-12-31 23:16:49 (3 years ago)
First seen 2017-05-21 21:04:38 (8 years ago)
Size 701 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 21:04:38 (8 years ago); latest analysis 2022-12-31 23:16:49 (3 years ago).

Publisher context

Product metadata: ANGLE 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 ANGLE libGLESv2 Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2022-12-31 23:16:49 (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: ANGLE libGLESv2 Dynamic Link Library
MD5: 2899808f52af4c068852f8328bc29716
Size: 701 KB
First Published: 2017-05-21 21:04:38 (8 years ago)
Latest Published: 2022-12-31 23:16:49 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-12-31 23:16:49 (3 years ago)
%localappdata%\browserair\application\47.0.0.5
%localappdata%\browserair\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.

15.4%
15.4%
15.4%
7.7%
7.7%
7.7%
7.7%
7.7%
7.7%
7.7%

The strongest geographic signal for this file is Portugal with 15.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 46.2%
Windows 10 30.8%
Windows 8.1 23.1%

The most common operating system signal for libglesv2.dll is Windows 7 with 46.2% 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 0x00070406
Image base 0x10000000

PE Sections:

Sections 5
Raw data 717312

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

.text 548352 bytes · 76.4% of section data
MD5 9d0b694a3bb4294e9942ede78415ce40
.rdata 136192 bytes · 19.0% of section data
MD5 6e71c6eb1a9aebd3e1139558ac4fb856
.data 7168 bytes · 1.0% of section data
MD5 04a4d06069726c57749b0d39542d8ab5
.rsrc 1536 bytes · 0.2% of section data
MD5 ebd4fb52d408091999ec137f79e5c44e
.reloc 24064 bytes · 3.4% of section data
MD5 7f39538102c47739c5e997b393733978

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 2899808f52af4c068852f8328bc29716.
  • 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.