GridinSoft Threat Intelligence

GLES_V2.dll file report

Under review File reputation report
MD5 beab92b8b99fdde28d6d465da32367ec
Latest seen 2025-01-20 23:01:03 (a year ago)
First seen 2024-06-02 23:00:58 (2 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-06-02 23:00:58 (2 years ago); latest analysis 2025-01-20 23:01:03 (a year ago).

Digital signature

Signed by Shanghai Baizhi Network Technology Co., Ltd.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

GLES_V2.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-01-20 23:01:03 (a year 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.

MD5: beab92b8b99fdde28d6d465da32367ec
Size: 2 MB
First Published: 2024-06-02 23:00:58 (2 years ago)
Latest Published: 2025-01-20 23:01:03 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-20 23:01:03 (a year ago)

The signature on GLES_V2.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%
%sysdrive%\ldplayer\ldplayer9

ThreatInfo has observed GLES_V2.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 GLES_V2.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.

GLES_V2.dll is identified as pe for 64-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x001fdc70
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 2820096

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

.text 2101760 bytes · 74.5% of section data
MD5 a6d08ede233b807c1880dfe3a593b6b8
.rdata 677888 bytes · 24.0% of section data
MD5 3059ce962372b6cd39ab612587b39b11
.data 7168 bytes · 0.3% of section data
MD5 84585a0a25f0ba5f300092b1c7104c54
.pdata 31232 bytes · 1.1% of section data
MD5 60ab2f1b9b4bdbfe6fea004f60bc2477
.rsrc 512 bytes · 0.0% of section data
MD5 69bd40c9c647787108fe126399c64e9a
.reloc 1536 bytes · 0.1% of section data
MD5 7a762e714cea0e50a0d94af215a81dc9

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