GridinSoft Threat Intelligence

libeay32.dll.Cover file report

Clean record File reputation report
MD5 5ed938f1925663cba4a529101fd43b72
Latest seen 2025-11-28 23:00:25 (6 months ago)
First seen 2017-05-21 03:02:09 (9 years ago)
Size 1 MB
Publisher The OpenSSL Project, http://www.openssl.org/
Product The OpenSSL Toolkit
Signed by Realtek Semiconductor Corp

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 03:02:09 (9 years ago); latest analysis 2025-11-28 23:00:25 (6 months ago).

Publisher context

Company metadata: The OpenSSL Project, http://www.openssl.org/. Product metadata: The OpenSSL Toolkit.

Digital signature

Signed by Realtek Semiconductor Corp. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

File context

libeay32.dll.Cover is a Windows file recorded in the ThreatInfo database. It is associated with The OpenSSL Toolkit. The reported company name is The OpenSSL Project, http://www.openssl.org/. The current detection status is Clean, based on the latest analysis from 2025-11-28 23:00:25 (6 months ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

File Details

Product Name: The OpenSSL Toolkit
Company Name: The OpenSSL Project, http://www.openssl.org/
MD5: 5ed938f1925663cba4a529101fd43b72
Size: 1 MB
First Published: 2017-05-21 03:02:09 (9 years ago)
Latest Published: 2025-11-28 23:00:25 (6 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-11-28 23:00:25 (6 months ago)

Overview

Signed By: Realtek Semiconductor Corp
Status: Valid

The signature on libeay32.dll.Cover 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.

Common Places:

%localappdata%\ucbrowser\user data\ucwifi\1.0.0.8
%programfiles%\ucbrowser\application\6.1.2015.1007
%programfiles%\ucbrowser\application\6.0.1308.1201
%programfiles%\wifisrv
%programfiles%\ucbrowser\application\5.7.16817.1002
%localappdata%\ucbrowser\user data_i18n\ucwifi\2.0.0.0
%programfiles%\ucbrowser\application\5.6.11651.1013\update\0\remote\0_beta_package\5.6.12265.1017
%programfiles%\ucbrowser\application\5.6.12265.1017
%programfiles%\ucbrowser\application\5.6.11651.1013
%programfiles%\ucbrowser\application\5.7.15533.1010

ThreatInfo has observed libeay32.dll.Cover 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.

File Names:

2 observed names
libeay32.dll libeay32.dll.Cover

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

ThreatInfo has seen libeay32.dll.Cover across 89 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 13.8%
Low High activity

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

OS Version:

Windows 7 50.1%
Windows 10 40.2%
Windows 8.1 6.1%
Windows 8 2.3%
Windows XP 0.9%
Windows Vista 0.2%
Windows Embedded 8.1 0.1%
Windows Server 2003 0.1%

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

Analysis

libeay32.dll.Cover 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 0x0009b756
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1118208

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

.text 737280 bytes · 65.9% of section data
MD5 dafd786f380bffe724c72fa8c58c66a5
.rdata 262144 bytes · 23.4% of section data
MD5 a1a9a9c5a40450ebc1e8658f6cf03408
.data 65536 bytes · 5.9% of section data
MD5 e150777e42df8308ee82424eaf90ff08
.rsrc 4096 bytes · 0.4% of section data
MD5 b484d1410577ef61b009b095aeb43cf6
.reloc 49152 bytes · 4.4% of section data
MD5 475b0b26ffb45ea0901400eaf32c3fdf

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 5ed938f1925663cba4a529101fd43b72.
  • 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.