GridinSoft Threat Intelligence

libglesv2.dll file report

Under review File reputation report
MD5 4073440179a4929a3e84145d9ce7009f
Latest seen 2022-02-27 23:09:14 (4 years ago)
First seen 2017-11-30 20:08:06 (8 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-11-30 20:08:06 (8 years ago); latest analysis 2022-02-27 23:09:14 (4 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-02-27 23:09:14 (4 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: 4073440179a4929a3e84145d9ce7009f
Size: 2 MB
First Published: 2017-11-30 20:08:06 (8 years ago)
Latest Published: 2022-02-27 23:09:14 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-02-27 23:09:14 (4 years ago)
%localappdata%\ucozmedia\uran\application\59.0.3071.110
%localappdata%\ucozmedia\uran\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.

Windows 10 52.1%
Windows 7 37.0%
Windows 8.1 11.0%

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

PE Sections:

Sections 7
Raw data 2937344

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

.text 2195456 bytes · 74.7% of section data
MD5 7c5c3e62d56cf66ad926b7d9eb322948
.rdata 624128 bytes · 21.2% of section data
MD5 c3c948cbc840496375b6b5e6b812bd49
.data 17408 bytes · 0.6% of section data
MD5 4afd4a2549f35e6f1f396124e4746541
.tls 512 bytes · 0.0% of section data
MD5 8e3343efa9afc26ac6caf49228cbe049
.gfids 3072 bytes · 0.1% of section data
Uncommon name
MD5 a84d1b8b097da0002ce65170ae19ece3
.rsrc 1536 bytes · 0.1% of section data
MD5 d0b8b8064eb5693ab1b2e4a37f161468
.reloc 95232 bytes · 3.2% of section data
MD5 2cca2c798ba97484bed2ce1f5f97df63

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 4073440179a4929a3e84145d9ce7009f.
  • 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.