GridinSoft Threat Intelligence

libGLES_CM_translator.dll file report

Under review File reputation report
MD5 cd01984568fa0ab798ce9e218898a8ee
Latest seen 2021-06-10 20:46:23 (4 years ago)
First seen 2019-04-17 04:13:28 (7 years ago)
Size 246 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-17 04:13:28 (7 years ago); latest analysis 2021-06-10 20:46:23 (4 years ago).

Digital signature

Signed by 北京文安卓立科技有限公司. 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.

libGLES_CM_translator.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-06-10 20:46:23 (4 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.

MD5: cd01984568fa0ab798ce9e218898a8ee
Size: 246 KB
First Published: 2019-04-17 04:13:28 (7 years ago)
Latest Published: 2021-06-10 20:46:23 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-10 20:46:23 (4 years ago)
Signed By: 北京文安卓立科技有限公司
Status: Valid

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

ThreatInfo has observed libGLES_CM_translator.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 8.1 50.0%
Windows 10 50.0%

The most common operating system signal for libGLES_CM_translator.dll is Windows 8.1 with 50.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.

libGLES_CM_translator.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 0x000010c0
Image base 0x66ec0000

PE Sections:

Sections 7
Raw data 243712

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

.text 179712 bytes · 73.7% of section data
MD5 a296440c3851427c1c9e6d9649ccad08
.data 16896 bytes · 6.9% of section data
MD5 40a5c7b44e02cbc69cedf1ca62625637
.rdata 15360 bytes · 6.3% of section data
MD5 4cb8c5d66e6bd3b7ea34800b773d3b3c
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 19968 bytes · 8.2% of section data
MD5 88f1c84e1bee98ab7a5eef19750359bd
.idata 1536 bytes · 0.6% of section data
MD5 f36d1117fc547ba1f2471cd3349f7b9f
.reloc 10240 bytes · 4.2% of section data
MD5 8741ec710fe62fff7549a8f3f8eba04c

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