GridinSoft Threat Intelligence

libGLESv2.dll file report

Under review File reputation report
MD5 498b01e3beed2e93ce02aa9ad37717c3
Latest seen 2021-01-07 12:38:18 (5 years ago)
First seen 2019-06-06 17:36:18 (6 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-06-06 17:36:18 (6 years ago); latest analysis 2021-01-07 12:38:18 (5 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 2021-01-07 12:38:18 (5 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: 498b01e3beed2e93ce02aa9ad37717c3
Size: 2 MB
First Published: 2019-06-06 17:36:18 (6 years ago)
Latest Published: 2021-01-07 12:38:18 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 12:38:18 (5 years ago)
%appdata%\windows
%appdata%\temp\sme2020\winroot\misa jsc\misa sme.net 2020\bin\x64
%appdata%\temp\misa.sme2019\winroot\misa jsc\misa sme.net 2020\bin\x64

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 60.0%
Windows 7 40.0%

The most common operating system signal for libGLESv2.dll is Windows 10 with 60.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 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 0x002003cc
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 2673664

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

.text 2289152 bytes · 85.6% of section data
MD5 6027f972cb8634bd704eb540b5cf2cc2
.rdata 278016 bytes · 10.4% of section data
MD5 975ba9f0a6eb316b99683252e1c2eea3
.data 12288 bytes · 0.5% of section data
MD5 4490ff2ad301e1d439bc7c91370f651c
.pdata 73728 bytes · 2.8% of section data
MD5 e5c136343391e6c53b6268a3875c236a
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 4c409915ee13dfdf25eabff1322059b9
.gfids 3072 bytes · 0.1% of section data
Uncommon name
MD5 96946801d0b0428acfc92be0499884c6
.tls 512 bytes · 0.0% of section data
MD5 60720ae4e3584c2f8ff87a0df634444d
.rsrc 1024 bytes · 0.0% of section data
MD5 4f0d0a0e116c46ddf07646c9bbe964bd
.reloc 15360 bytes · 0.6% of section data
MD5 58c6ec78c75bf7c5d3cbfabd5fef06ac

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 498b01e3beed2e93ce02aa9ad37717c3.
  • 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.