GridinSoft Threat Intelligence

libeay32.dll file report

Under review File reputation report
MD5 6bd91a3a571c65072e0416cc495d9774
Latest seen 2026-05-09 23:01:06 (2 weeks ago)
First seen 2017-05-22 05:03:10 (9 years ago)
Size 996 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 05:03:10 (9 years ago); latest analysis 2026-05-09 23:01:06 (2 weeks ago).

Publisher context

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

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.

libeay32.dll 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 Undefined, based on the latest analysis from 2026-05-09 23:01:06 (2 weeks 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: The OpenSSL Toolkit
Company Name: The OpenSSL Project, http://www.openssl.org/
MD5: 6bd91a3a571c65072e0416cc495d9774
Size: 996 KB
First Published: 2017-05-22 05:03:10 (9 years ago)
Latest Published: 2026-05-09 23:01:06 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-09 23:01:06 (2 weeks ago)
%programfiles%\driver identifier
%programfiles%

ThreatInfo has observed libeay32.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 48.5%
Windows 10 41.6%
Windows 8.1 5.8%
Windows XP 2.4%
Windows 8 1.2%
Windows Vista 0.3%
Windows Server 2003 0.1%
Windows Server 2012 R2 0.1%

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

libeay32.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 0x0009e95c
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1019392

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

.text 647168 bytes · 63.5% of section data
MD5 c7d046eb6c494d34d47f78931c6f1a4c
.rdata 265216 bytes · 26.0% of section data
MD5 ca2ccb1466ccf4023ef28c26c40bcc62
.data 60928 bytes · 6.0% of section data
MD5 0cc455bb9b45c31ae2160460496357b7
.rsrc 2048 bytes · 0.2% of section data
MD5 5a06d42d1e643fa87297c32fea16471f
.reloc 44032 bytes · 4.3% of section data
MD5 9bfd5d9df84f950c615fc55fe6c84ed8

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 6bd91a3a571c65072e0416cc495d9774.
  • 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.