GridinSoft Threat Intelligence

libglesv2.dll file report

Under review File reputation report
MD5 c0e50547b5abf7b9c7da9bcb01646f91
Latest seen 2022-08-03 23:52:44 (3 years ago)
First seen 2020-11-13 04:19:26 (5 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-11-13 04:19:26 (5 years ago); latest analysis 2022-08-03 23:52:44 (3 years 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 2022-08-03 23:52:44 (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: SwiftShader libGLESv2 Dynamic Link Library
MD5: c0e50547b5abf7b9c7da9bcb01646f91
Size: 2 MB
First Published: 2020-11-13 04:19:26 (5 years ago)
Latest Published: 2022-08-03 23:52:44 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-03 23:52:44 (3 years ago)
%localappdata%\orbitum\application\80.0.3987.123

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 66.7%
Windows 7 33.3%

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

PE Sections:

Sections 8
Raw data 3010560

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

.text 2682880 bytes · 89.1% of section data
MD5 2931982d99e0c26b3175b3ce29566261
.rdata 250368 bytes · 8.3% of section data
MD5 eb39c58e57edd7f9adc63f491f1467df
.data 7168 bytes · 0.2% of section data
MD5 e46951efeb0086f050cbce1a264663a1
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 826f40119e04ae53ba586e6d09044e00
.tls 512 bytes · 0.0% of section data
MD5 adb00c88d5919bab3c4b160cbf2abed5
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 c003b38f986d4548387086876871e22d
.rsrc 1024 bytes · 0.0% of section data
MD5 cf06273380dbf1d697293d3b6f611e1d
.reloc 67584 bytes · 2.2% of section data
MD5 8d332e8c4dacc776a57133dbcb92ba41

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 c0e50547b5abf7b9c7da9bcb01646f91.
  • 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.