GridinSoft Threat Intelligence

libGLESv2.dll file report

Under review File reputation report
MD5 d332424da1c29872c84e5700410944bc
Latest seen 2025-09-25 23:05:48 (8 months ago)
First seen 2020-08-08 15:05:58 (5 years ago)
Size 3 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-08-08 15:05:58 (5 years ago); latest analysis 2025-09-25 23:05:48 (8 months 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 2025-09-25 23:05:48 (8 months 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: d332424da1c29872c84e5700410944bc
Size: 3 MB
First Published: 2020-08-08 15:05:58 (5 years ago)
Latest Published: 2025-09-25 23:05:48 (8 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-09-25 23:05:48 (8 months ago)
%localappdata%\popcorn-time

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 64-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 64-bit
Subsystem Windows CUI
Entry point 0x00317330
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 3770880

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

.text 3421696 bytes · 90.7% of section data
MD5 b921f99edd69f4731e2d01877cab02a8
.rdata 257536 bytes · 6.8% of section data
MD5 5978b6c664639e04ed248f74415f38f0
.data 8192 bytes · 0.2% of section data
MD5 dc394c45888a24ce17c4f394a301dad9
.pdata 67584 bytes · 1.8% of section data
MD5 a182ffbf433b3a69adf0158af762b807
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 3a2b7e4ce065004ced1fe64e8d62221e
.tls 512 bytes · 0.0% of section data
MD5 60720ae4e3584c2f8ff87a0df634444d
.rsrc 1024 bytes · 0.0% of section data
MD5 315e9915c4e3d6115bf18d8f38895e1f
.reloc 13824 bytes · 0.4% of section data
MD5 28f1bc0f96fe42f9c4311872e337d7e9

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