ssleay32(45).dll file report

MD5 2cbb35ffc48e3343fbb85a12ef912716
Latest seen 2023-07-26 23:50:19 (2 years ago)
First seen 2017-05-21 14:09:41 (8 years ago)
Size 267 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 14:09:41 (8 years ago); latest analysis 2023-07-26 23:50:19 (2 years ago).

Publisher context

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

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. 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.

ssleay32(45).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 2023-07-26 23:50:19 (2 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.

Product Name: The OpenSSL Toolkit
Company Name: The OpenSSL Project, http://www.openssl.org/
MD5: 2cbb35ffc48e3343fbb85a12ef912716
Size: 267 KB
First Published: 2017-05-21 14:09:41 (8 years ago)
Latest Published: 2023-07-26 23:50:19 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-07-26 23:50:19 (2 years ago)
%programfiles%\qksee
%programfiles%\winzipper
%programfiles%\picexa
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%

ThreatInfo has observed ssleay32(45).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.

ssleay32.dll
ssleay32(171).dll
ssleay32(153).dll
ssleay32(28).dll
ssleay32(45).dll

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.

14.0%
10.2%
9.1%
8.6%
7.5%
7.0%
6.5%
5.4%
4.8%
4.8%
3.2%
2.2%
2.2%
1.6%
1.6%
1.1%
1.1%
1.1%
1.1%
1.1%
1.1%
1.1%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%

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

Windows 7 67.0%
Windows XP 16.0%
Windows 8.1 8.5%
Windows 8 4.8%
Windows 10 3.2%
Windows Vista 0.5%

The most common operating system signal for ssleay32(45).dll is Windows 7 with 67.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.

ssleay32(45).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: 0x0003213f

PE Sections:

Name Size of data MD5
.text 202752 f1a3eed346f714867a82970b0fa54452
.rdata 46080 329ab3620480db67cb16b48603bf5194
.data 12288 dfc45cdac0d35ff5bf284ea1c68662d0
.rsrc 1536 41ff55d2f27629e0760820c031fcf9bb
.reloc 9728 da8232cf925305392d305d1aa6ad9a84

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: