libEGL.dll threat report

MD5 42e73b1ac6b75bb470e36df3ef9cc246
Latest seen 2026-05-04 23:00:41 (18 hours ago)
First seen 2025-12-10 23:01:55 (5 months ago)
Size 369 KB

This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for libEGL.dll. ThreatInfo currently classifies this sample as Adware.OneBrowser.

GridinSoft Anti-Malware detection

GridinSoft already detects this file

The latest ThreatInfo record shows libEGL.dll detected as Adware.OneBrowser. You can download GridinSoft Anti-Malware to scan the system and remove this detection if the file is present on your device.

Detection name
Adware.OneBrowser
Last analysis
2026-05-04 23:00:41 (18 hours ago)
File hash
42e73b1ac6b75bb470e36df3ef9cc246
Download Anti-Malware

libEGL.dll is a Windows file recorded in the ThreatInfo database. It is associated with ANGLE libEGL Dynamic Link Library. The current detection status is Adware.OneBrowser, based on the latest analysis from 2026-05-04 23:00:41 (18 hours ago).

If libEGL.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Adware.OneBrowser.

Product Name: ANGLE libEGL Dynamic Link Library
MD5: 42e73b1ac6b75bb470e36df3ef9cc246
Size: 369 KB
First Published: 2025-12-10 23:01:55 (5 months ago)
Latest Published: 2026-05-04 23:00:41 (18 hours ago)
Status: Adware.OneBrowser (on last analysis)
Analysis Date: 2026-05-04 23:00:41 (18 hours ago)
libEGL.dll detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Chickadee Digital, LLC
Status: Valid

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.

%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application
%programfiles%\onebrowser\application

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.

23.8%
19.0%
9.5%
9.5%
4.8%
4.8%
4.8%
4.8%
4.8%
4.8%
4.8%
4.8%

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

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 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: 0x0001fe30

PE Sections:

Name Size of data MD5
.text 268800 77970fc2c2e55705c268992acf458ec3
.rdata 63488 581453db9e0dc5202ff44783c114ee32
.data 7168 b448e8ca22194465779d4031a5bad350
.00cfg 512 5ce031225ef8916a987630a64d2459dd
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 1536 798c1b9314988af0d7aab694c49132b6
.reloc 14848 50d92549f01463e50314023986413f63

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: