GridinSoft Threat Intelligence

libGLESv2.dll file report

Under review File reputation report
MD5 efdaae461514d3669d22cc61b3aa87ff
Latest seen 2023-05-04 23:23:37 (3 years ago)
First seen 2020-10-13 11:57:49 (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-10-13 11:57:49 (5 years ago); latest analysis 2023-05-04 23:23:37 (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 2023-05-04 23:23:37 (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: efdaae461514d3669d22cc61b3aa87ff
Size: 2 MB
First Published: 2020-10-13 11:57:49 (5 years ago)
Latest Published: 2023-05-04 23:23:37 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-05-04 23:23:37 (3 years ago)
%commonappdata%\ubar\ubar\modules\cef

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 100.0%

The most common operating system signal for libGLESv2.dll is Windows 10 with 100.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 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 0x00267531
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 2683904 bytes · 89.1% of section data
MD5 b37870a737dca108d0e76e811d84b93b
.rdata 248832 bytes · 8.3% of section data
MD5 133f7a7491d50aa3af046e061ec40760
.data 7168 bytes · 0.2% of section data
MD5 86cbfeae72ad7b1f5a8caeddcd887824
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 73ba68fbf582dd31918b843a31eefa82
.tls 512 bytes · 0.0% of section data
MD5 b30464e69ecc4f2c756fa8ff158a38f1
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 c003b38f986d4548387086876871e22d
.rsrc 1024 bytes · 0.0% of section data
MD5 cf06273380dbf1d697293d3b6f611e1d
.reloc 68096 bytes · 2.3% of section data
MD5 1819147ec088abe1d656ce7ea8cd22e7

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