GridinSoft Threat Intelligence

libssl-1_1.dll file report

Under review File reputation report
MD5 0bc4df79b2752dd03c2e04c0d3f4aea1
Latest seen 2026-02-04 23:01:15 (3 months ago)
First seen 2020-12-12 13:05:15 (5 years ago)
Size 518 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-12-12 13:05:15 (5 years ago); latest analysis 2026-02-04 23:01:15 (3 months ago).

Publisher context

Company metadata: The OpenSSL Project, https://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.

libssl-1_1.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, https://www.openssl.org/. The current detection status is Undefined, based on the latest analysis from 2026-02-04 23:01:15 (3 months 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, https://www.openssl.org/
MD5: 0bc4df79b2752dd03c2e04c0d3f4aea1
Size: 518 KB
First Published: 2020-12-12 13:05:15 (5 years ago)
Latest Published: 2026-02-04 23:01:15 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-04 23:01:15 (3 months ago)
%profile%
%localappdata%
%programfiles%

ThreatInfo has observed libssl-1_1.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 89.1%
Windows 7 8.3%
Windows 8.1 2.3%
Windows 8 0.3%

The most common operating system signal for libssl-1_1.dll is Windows 10 with 89.1% 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.

libssl-1_1.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00001c7b
Image base 0x10000000

PE Sections:

Sections 7
Raw data 529408

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

.text 387584 bytes · 73.2% of section data
MD5 96612d392c89c0d3d034ccef280f6ff2
.rdata 92160 bytes · 17.4% of section data
MD5 db8a5b52c6811ddd3ee225b4ecf965ba
.data 14336 bytes · 2.7% of section data
MD5 ac3efa331effbf19c91a8454b4343084
.idata 16896 bytes · 3.2% of section data
MD5 a62caf9b323b85aead1e8f1f795c661d
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 fc843c1bc91ff9859bb59fe3dcc4c2d3
.rsrc 2048 bytes · 0.4% of section data
MD5 76d5b83f0c26cdefcdfbd25c01fba407
.reloc 15872 bytes · 3.0% of section data
MD5 4c80ceb7dfd6294703f562a3912f5aac

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 0bc4df79b2752dd03c2e04c0d3f4aea1.
  • 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.