GridinSoft Threat Intelligence

libcrypto-1_1.dll file report

Under review File reputation report
MD5 d5a5e2b8e937e31c881dafd4179f5536
Latest seen 2026-02-04 23:01:11 (3 months ago)
First seen 2020-12-12 13:07:26 (5 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-12-12 13:07:26 (5 years ago); latest analysis 2026-02-04 23:01:11 (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.

libcrypto-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:11 (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: d5a5e2b8e937e31c881dafd4179f5536
Size: 2 MB
First Published: 2020-12-12 13:07:26 (5 years ago)
Latest Published: 2026-02-04 23:01:11 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-04 23:01:11 (3 months ago)
%profile%
%localappdata%
%programfiles%

ThreatInfo has observed libcrypto-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.3%
Windows 7 8.1%
Windows 8.1 2.3%
Windows 8 0.3%

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

libcrypto-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 0x000047ff
Image base 0x10000000

PE Sections:

Sections 7
Raw data 2506240

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

.text 1851904 bytes · 73.9% of section data
MD5 00557a0d5391dc10e289c0960bfac319
.rdata 578560 bytes · 23.1% of section data
MD5 df6af6cfa8f756bf383fcf85b72054e5
.data 5632 bytes · 0.2% of section data
MD5 a9e9cd3cbe2acb7c9ff4272934cba24e
.idata 6656 bytes · 0.3% of section data
MD5 66a4870b120d2d21bd2261e759f09a1b
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 6b8f1453883fd8f932bd8f4631cfc036
.rsrc 2048 bytes · 0.1% of section data
MD5 bfb3dce37ddcf63be754c1952d4323f1
.reloc 60928 bytes · 2.4% of section data
MD5 3315f353bf5f857190deb161e00a6452

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