GridinSoft Threat Intelligence

libegl.dll file report

Under review File reputation report
MD5 33467443bc708c47440555dce89da4f3
Latest seen 2021-01-09 07:46:04 (5 years ago)
First seen 2019-03-05 13:26:50 (7 years ago)
Size 106 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-03-05 13:26:50 (7 years ago); latest analysis 2021-01-09 07:46:04 (5 years ago).

Publisher context

Product metadata: SwiftShader libEGL 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.

libegl.dll is a Windows file recorded in the ThreatInfo database. It is associated with SwiftShader libEGL Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2021-01-09 07:46:04 (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 libEGL Dynamic Link Library
MD5: 33467443bc708c47440555dce89da4f3
Size: 106 KB
First Published: 2019-03-05 13:26:50 (7 years ago)
Latest Published: 2021-01-09 07:46:04 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-09 07:46:04 (5 years ago)
%localappdata%\good chrome\application\64.17.3282.140
%localappdata%\good chrome\temp\source3748_8827\goodchrome-bin\64.17.3282.140

ThreatInfo has observed libegl.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 7 44.8%
Windows 10 37.9%
Windows 8.1 17.2%

The most common operating system signal for libegl.dll is Windows 7 with 44.8% 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.

libegl.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 0x00006b56
Image base 0x10000000

PE Sections:

Sections 7
Raw data 107520

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

.text 69120 bytes · 64.3% of section data
MD5 69701ab904968542318090ef42009b92
.rdata 28160 bytes · 26.2% of section data
MD5 779a664f98cd0720e42939f539e364d8
.data 2560 bytes · 2.4% of section data
MD5 380b07138e15d0879780fdf9647cd3dc
.tls 512 bytes · 0.5% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.gfids 512 bytes · 0.5% of section data
Uncommon name
MD5 da5124cd71b5745949ead9eeaa1677b3
.rsrc 1536 bytes · 1.4% of section data
MD5 38e3680ef066c51ddeb76039b0d5bcf4
.reloc 5120 bytes · 4.8% of section data
MD5 208d5bac512b8a3cf1534b6ec1a9e272

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 33467443bc708c47440555dce89da4f3.
  • 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.