GridinSoft Threat Intelligence

libcrypto-1_1.dll file report

Under review File reputation report
MD5 befa05c8ec945458a7730a544b777ac4
Latest seen 2023-02-20 23:03:44 (3 years ago)
First seen 2021-02-25 16:24:03 (5 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-02-25 16:24:03 (5 years ago); latest analysis 2023-02-20 23:03:44 (3 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.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-02-20 23:03:44 (3 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: befa05c8ec945458a7730a544b777ac4
Size: 2 MB
First Published: 2021-02-25 16:24:03 (5 years ago)
Latest Published: 2023-02-20 23:03:44 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-20 23:03:44 (3 years ago)
%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 100.0%

The most common operating system signal for libcrypto-1_1.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.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 0x00004822
Image base 0x10000000

PE Sections:

Sections 7
Raw data 2515456

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

.text 1849344 bytes · 73.5% of section data
MD5 5dda42fd53f33682f48259c5f5e5afb8
.rdata 589824 bytes · 23.4% of section data
MD5 414906591772357aafaf18cc361dbb9f
.data 5632 bytes · 0.2% of section data
MD5 78744481c482031ff66f6225dc9ea604
.idata 6656 bytes · 0.3% of section data
MD5 6b1c42ccb56676c55be2a8b5403b91d5
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 6533fef78cac0453e780f11a4fd6b284
.rsrc 2048 bytes · 0.1% of section data
MD5 710b2838afaa16f190471cee278e44cf
.reloc 61440 bytes · 2.4% of section data
MD5 e609396776657acd7325af7bfa1d6f66

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