libglesv2.dll file report

MD5 0c1e0e2c32fa30370a6f8c9fca122548
Latest seen 2024-12-19 23:03:23 (a year ago)
First seen 2017-05-21 10:03:24 (8 years ago)
Size 1 MB
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 10:03:24 (8 years ago); latest analysis 2024-12-19 23:03:23 (a year ago).

Publisher context

Product metadata: ANGLE libGLESv2 Dynamic Link Library.

Digital signature

Signed by Google Inc. 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. 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 ANGLE libGLESv2 Dynamic Link Library. The current detection status is Clean, based on the latest analysis from 2024-12-19 23:03:23 (a year 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: ANGLE libGLESv2 Dynamic Link Library
MD5: 0c1e0e2c32fa30370a6f8c9fca122548
Size: 1 MB
First Published: 2017-05-21 10:03:24 (8 years ago)
Latest Published: 2024-12-19 23:03:23 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-12-19 23:03:23 (a year ago)
Signed By: Google Inc
Status: Valid

The signature on libglesv2.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.

%appdata%\chportu\app\chrome-bin\39.0.2171.95
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin
%appdata%\chportu\app\chrome-bin

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.

18.1%
7.5%
7.0%
6.5%
5.5%
4.5%
4.5%
4.0%
3.0%
3.0%
2.5%
2.5%
2.0%
1.5%
1.5%
1.5%
1.5%
1.5%
1.5%
1.5%
1.5%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%

The strongest geographic signal for this file is Turkey with 18.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 61.7%
Windows 7 29.9%
Windows 8.1 7.0%
Windows 8 1.0%
Windows Vista 0.5%

The most common operating system signal for libglesv2.dll is Windows 10 with 61.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 32 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x0007a7dd

PE Sections:

Name Size of data MD5
.text 826880 a8922c0f3eb23e6d813b485d80f8bd6e
.rdata 205824 4eb65f417d57483c691ee6bbead865cc
.data 7168 bdc8630b1b2a1dddf9798bdb164bf9bc
.rsrc 1536 ed1a7e8d711f8abc1b4544a3a7152f59
.reloc 28160 715abb25fa12b6bedc721b4b4062c06f

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.

More information: