GridinSoft Threat Intelligence

libeay32.dll file report

Under review File reputation report
MD5 1f3d6ea5e7dab4126b5315261785408b
Latest seen 2026-04-17 23:00:15 (a month ago)
First seen 2017-05-28 01:03:18 (9 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 01:03:18 (9 years ago); latest analysis 2026-04-17 23:00:15 (a month 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-04-17 23:00:15 (a month 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: 1f3d6ea5e7dab4126b5315261785408b
Size: 1 MB
First Published: 2017-05-28 01:03:18 (9 years ago)
Latest Published: 2026-04-17 23:00:15 (a month ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-04-17 23:00:15 (a month ago)
%programfiles%\flip shopping catalog
%programfiles%\packetsender
%programfiles%\dream\dreamboxedit
%programfiles%\bayorganizer
%programfiles%
%programfiles%\momentum\resources\nzbget
%appdata%\system

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 10 80.6%
Windows 7 12.9%
Windows 8.1 4.8%
Windows 8 1.6%

The most common operating system signal for libeay32.dll is Windows 10 with 80.6% 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 0x000d76c3
Image base 0x11000000

PE Sections:

Sections 5
Raw data 1363456

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

.text 936960 bytes · 68.7% of section data
MD5 acae240760ef201d7f397e9b8324dde0
.rdata 350208 bytes · 25.7% of section data
MD5 beed3c764446c2eb25fb1aecf46d742c
.data 29696 bytes · 2.2% of section data
MD5 a5c307c577d75230177e3999778dbf08
.rsrc 1536 bytes · 0.1% of section data
MD5 abc24922c990494d61bda666dd045fc3
.reloc 45056 bytes · 3.3% of section data
MD5 62410d588d7e361bb4a491e4bca7c721

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 1f3d6ea5e7dab4126b5315261785408b.
  • 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.