GridinSoft Threat Intelligence

libglesv2.dll file report

Clean record File reputation report
MD5 39c3d19d5ccd0eb79b6a568613a9a11c
Latest seen 2023-01-06 23:38:56 (3 years ago)
First seen 2018-09-12 16:12:21 (7 years ago)
Size 2 MB
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-09-12 16:12:21 (7 years ago); latest analysis 2023-01-06 23:38:56 (3 years ago).

Publisher context

Product metadata: SwiftShader libGLESv2 Dynamic Link Library.

Digital signature

Signed by Google Inc. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

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 Clean, based on the latest analysis from 2023-01-06 23:38:56 (3 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: SwiftShader libGLESv2 Dynamic Link Library
MD5: 39c3d19d5ccd0eb79b6a568613a9a11c
Size: 2 MB
First Published: 2018-09-12 16:12:21 (7 years ago)
Latest Published: 2023-01-06 23:38:56 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-01-06 23:38:56 (3 years ago)
Signed By: Google Inc
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%appdata%\view\chrome\application\67.0.3396.87
%profile%\lavbuh\application data\view\chrome\application\67.0.3396.87

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 63.3%
Windows 7 33.3%
Windows XP 3.3%

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

PE Sections:

Sections 5
Raw data 2234880

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

.text 1901056 bytes · 85.1% of section data
MD5 d6c8dde75f00d5c6dd95ab748c153b9c
.rdata 252416 bytes · 11.3% of section data
MD5 9950ba469047ad36e09aefc53e86306d
.data 11264 bytes · 0.5% of section data
MD5 4dd19c8275002f9780421a610f0aed6b
.rsrc 1024 bytes · 0.0% of section data
MD5 c8a39b48689ace086ac1b5da0fd114a7
.reloc 69120 bytes · 3.1% of section data
MD5 5c2e87a8bc464068b7e69bf44d9fa900

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 39c3d19d5ccd0eb79b6a568613a9a11c.
  • 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.