GridinSoft Threat Intelligence
libeay32.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-05-26 08:01:51 (9 years ago); latest analysis 2021-04-19 20:54:54 (5 years ago).
Company metadata: The OpenSSL Project, http://www.openssl.org/. Product metadata: The OpenSSL Toolkit.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
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 2021-04-19 20:54:54 (5 years 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.
File Details
| Product Name: | The OpenSSL Toolkit |
| Company Name: | The OpenSSL Project, http://www.openssl.org/ |
| MD5: | 7f0e965e1142a328727e6b0fbbfaea17 |
| Size: | 1 MB |
| First Published: | 2017-05-26 08:01:51 (9 years ago) |
| Latest Published: | 2021-04-19 20:54:54 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-04-19 20:54:54 (5 years ago) |
Common Places:
| %localappdata%\freeu\application\56.1.2924.38\freeu_helper |
| %localappdata%\freeu\application\56.1.2924.62\freeu_helper |
| %localappdata%\freeu\application\56.1.2924.71\freeu_helper |
| %localappdata%\freeu\application\56.1.2924.82\freeu_helper |
| %localappdata%\freeu\application\56.1.2924.93\freeu_helper |
| %localappdata%\freeu\application\56.1.2924.93 |
| %appdata%\tp |
| %localappdata%\freeu\application\56.1.2924.71 |
| %localappdata%\freeu\application\56.1.2924.82 |
| %localappdata%\freeu\application\56.1.2924.62 |
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.
Geographic signal
Observed country distribution
ThreatInfo has seen libeay32.dll across 10 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Ukraine with 83.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for libeay32.dll is Windows 10 with 52.7% 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 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
a5175ab7636f75554e00ae1621869a0c
8447f380598e9f3133a4a31e4cba0153
2c1d38331822a623c7478f426a6ab2be
00000000000000000000000000000000
5a705cf98cedb530d6acd230e6d9baf5
f08a1e5519652689153f92c90339f4e8
218e12d781a40bb9cafcef13c3420518
c969bec4f654df77b9dc143ee25039e5
7f781a59d669d92e08d2e208a1a3157d
2b60ab78214309dab33cf95c72292555
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.