GridinSoft Threat Intelligence

ssleay32.dll file report

Under review File reputation report
MD5 9dda5482e967ac23207405a20c74a370
Latest seen 2021-11-30 21:20:23 (4 years ago)
First seen 2017-05-21 15:02:54 (9 years ago)
Size 262 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 15:02:54 (9 years ago); latest analysis 2021-11-30 21:20:23 (4 years 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.

ssleay32.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-11-30 21:20:23 (4 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: 9dda5482e967ac23207405a20c74a370
Size: 262 KB
First Published: 2017-05-21 15:02:54 (9 years ago)
Latest Published: 2021-11-30 21:20:23 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-30 21:20:23 (4 years ago)
%localappdata%\vghd\bin
%localappdata%\vghd
%profile%\dmin\local settings\application data\vghd

ThreatInfo has observed ssleay32.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 68.2%
Windows 7 16.4%
Windows 8.1 10.3%
Windows 8 3.8%
Windows Vista 0.7%
Windows XP 0.7%

The most common operating system signal for ssleay32.dll is Windows 10 with 68.2% 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.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 0x00030fa1
Image base 0x10000000

PE Sections:

Sections 5
Raw data 267264

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

.text 198656 bytes · 74.3% of section data
MD5 720533ca5a6843b4df4ab14e85834d2f
.rdata 46080 bytes · 17.2% of section data
MD5 b8d5b3a81512ed42fed2a3c784308072
.data 11776 bytes · 4.4% of section data
MD5 e9ad068301ab79a8f6cc857a3e5f87bd
.rsrc 1536 bytes · 0.6% of section data
MD5 53896fdcb6f80affeb16baa0cde7d0a8
.reloc 9216 bytes · 3.4% of section data
MD5 b16f135982f42c660d27db4e5c7ea6d5

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 9dda5482e967ac23207405a20c74a370.
  • 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.