GridinSoft Threat Intelligence

libegl.dll file report

Under review File reputation report
MD5 396ba9407206f1c1073faaebeec17862
Latest seen 2025-06-16 23:01:13 (11 months ago)
First seen 2025-06-16 23:01:11 (11 months ago)
Size 25 KB
Product libEGL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-16 23:01:11 (11 months ago); latest analysis 2025-06-16 23:01:13 (11 months ago).

Publisher context

Product metadata: libEGL.

Digital signature

Signed by Beijing Sogou Technology Development Co., Ltd.. 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.

libegl.dll is a Windows file recorded in the ThreatInfo database. It is associated with libEGL. The current detection status is Undefined, based on the latest analysis from 2025-06-16 23:01:13 (11 months 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: libEGL
MD5: 396ba9407206f1c1073faaebeec17862
Size: 25 KB
First Published: 2025-06-16 23:01:11 (11 months ago)
Latest Published: 2025-06-16 23:01:13 (11 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-06-16 23:01:13 (11 months ago)

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

%localappdata%\sogoupdf\ktool_update\kdownload
%localappdata%

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 10 100.0%

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

libegl.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x000017c6
Image base 0x10000000

PE Sections:

Sections 5
Raw data 15360

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

.text 4608 bytes · 30.0% of section data
MD5 e48b861c3ed50aac37d29e90ef2ec659
.rdata 8192 bytes · 53.3% of section data
MD5 9b6d4b1300e8d00a837fc252d51402e5
.data 512 bytes · 3.3% of section data
MD5 bfcdd9374007569a72a55e928d02fa3f
.rsrc 1536 bytes · 10.0% of section data
MD5 4219df960fea94568ce3fba37dd1a3e1
.reloc 512 bytes · 3.3% of section data
MD5 4e642322c19ff968d49d44436b99d652

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 396ba9407206f1c1073faaebeec17862.
  • 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.