GridinSoft Threat Intelligence

libcrypto-1_1-x64.dll file report

Under review File reputation report
MD5 0c665f5b21f78b672720942dc603112e
Latest seen 2023-12-02 23:31:47 (2 years ago)
First seen 2020-10-20 13:22:08 (5 years ago)
Size 3 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-20 13:22:08 (5 years ago); latest analysis 2023-12-02 23:31:47 (2 years 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-x64.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 2023-12-02 23:31:47 (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, https://www.openssl.org/
MD5: 0c665f5b21f78b672720942dc603112e
Size: 3 MB
First Published: 2020-10-20 13:22:08 (5 years ago)
Latest Published: 2023-12-02 23:31:47 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-02 23:31:47 (2 years ago)
%commonappdata%\package

ThreatInfo has observed libcrypto-1_1-x64.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 100.0%

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

libcrypto-1_1-x64.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x00007090
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 3403264

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

.text 2393600 bytes · 70.3% of section data
MD5 b359a8abb46e28998bd7e08af9f78a5d
.rdata 841728 bytes · 24.7% of section data
MD5 b8f92c0fed7c0ebafd263cad682eedec
.data 11264 bytes · 0.3% of section data
MD5 7b607fe0abb5550db5ee0b9b0edeca01
.pdata 113664 bytes · 3.3% of section data
MD5 b07564cfc02b4de8969bc182aed8c0cd
.idata 9216 bytes · 0.3% of section data
MD5 71e4155f87f01d73ddf0f6a7a7942615
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 bde842e69578e6d6cd12dcbf598208a0
.rsrc 2048 bytes · 0.1% of section data
MD5 6e1d0ea61e76b5d4eb07bf08e0182e81
.reloc 31232 bytes · 0.9% of section data
MD5 3caf0070e881f7ffa8d7801fb96a3632

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