GridinSoft Threat Intelligence

libcrypto-1_1.dll file report

Under review File reputation report
MD5 f77ebf3bb87a6b7e6fc52071609cd88e
Latest seen 2026-03-05 23:01:04 (2 months ago)
First seen 2020-06-27 18:42:08 (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-06-27 18:42:08 (5 years ago); latest analysis 2026-03-05 23:01:04 (2 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-03-05 23:01:04 (2 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: f77ebf3bb87a6b7e6fc52071609cd88e
Size: 2 MB
First Published: 2020-06-27 18:42:08 (5 years ago)
Latest Published: 2026-03-05 23:01:04 (2 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-03-05 23:01:04 (2 months ago)
%programfiles%
%commonappdata%\totalav\updates\5_17_470

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 86.2%
Windows 7 10.3%
Windows 8.1 2.8%
Windows Server 2012 R2 0.3%
Windows Vista 0.2%
Windows Server 2008 R2 0.2%

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

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

PE Sections:

Sections 6
Raw data 2649088

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

.text 1940992 bytes · 73.3% of section data
MD5 4a9008065552a8f4bdbfb74f28529f9c
.rdata 622080 bytes · 23.5% of section data
MD5 57cd39cd5fb573c1afd10d29e90276df
.data 11776 bytes · 0.4% of section data
MD5 5bf8254d8ba63ae419814e2c87ea579e
.idata 5632 bytes · 0.2% of section data
MD5 e480533c17bf432480b89eae970a40ae
.rsrc 2048 bytes · 0.1% of section data
MD5 807e98a18a208b699c3850e500af7329
.reloc 66560 bytes · 2.5% of section data
MD5 c985af63c6741adfa5d126f66273c462

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