GridinSoft Threat Intelligence

libOpenglRender.dll file report

Under review File reputation report
MD5 c713d1bd5020b7ce74026eb15e074dce
Latest seen 2021-06-10 20:30:42 (4 years ago)
First seen 2019-04-17 04:18:47 (7 years ago)
Size 253 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-17 04:18:47 (7 years ago); latest analysis 2021-06-10 20:30:42 (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.

libOpenglRender.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:30:42 (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: c713d1bd5020b7ce74026eb15e074dce
Size: 253 KB
First Published: 2019-04-17 04:18:47 (7 years ago)
Latest Published: 2021-06-10 20:30:42 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-10 20:30:42 (4 years ago)
Signed By: 北京文安卓立科技有限公司
Status: Valid

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

libOpenglRender.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 0x64a80000

PE Sections:

Sections 7
Raw data 251392

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

.text 198144 bytes · 78.8% of section data
MD5 fa1ed7698e2acee5b0dc7034198ba168
.data 16896 bytes · 6.7% of section data
MD5 7255d4f6f4046b558098676d39d561be
.rdata 24576 bytes · 9.8% of section data
MD5 a54904a03cdc379b3f5000dd03dee494
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 0.2% of section data
MD5 021757f5b6297f9e9541ca6ea3402a03
.idata 3072 bytes · 1.2% of section data
MD5 a3b944cf03cbf03c3426c59315837412
.reloc 8192 bytes · 3.3% of section data
MD5 8f6d9418d7829b143097bb0cf300767a

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