GridinSoft Threat Intelligence

libssl-1_1-x64.dll file report

Under review File reputation report
MD5 fb948538916a35fbbf2bc471789ad946
Latest seen 2023-12-24 23:37:27 (2 years ago)
First seen 2020-10-20 13:14:26 (5 years ago)
Size 666 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-20 13:14:26 (5 years ago); latest analysis 2023-12-24 23:37:27 (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.

libssl-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-24 23:37:27 (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: fb948538916a35fbbf2bc471789ad946
Size: 666 KB
First Published: 2020-10-20 13:14:26 (5 years ago)
Latest Published: 2023-12-24 23:37:27 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-24 23:37:27 (2 years ago)
%commonappdata%\package

ThreatInfo has observed libssl-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 libssl-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.

libssl-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 0x00002518
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 681472

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

.text 468992 bytes · 68.8% of section data
MD5 b5cf2dcd5dab1018a43f9cfd0dfc3a52
.rdata 140800 bytes · 20.7% of section data
MD5 64467a7383d3143a6fd256ec669bf610
.data 17408 bytes · 2.6% of section data
MD5 9455cfb5bffe3cef3a2bce6cffaf1dca
.pdata 22016 bytes · 3.2% of section data
MD5 d04d481715bdd5407fa29fb0a8b531de
.idata 22528 bytes · 3.3% of section data
MD5 3abd5b05c55458f19d907a651090e276
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 868d691304b3eecfd927293201aafd36
.rsrc 2048 bytes · 0.3% of section data
MD5 f7cb8e519a32ee878b466095750c4d87
.reloc 7168 bytes · 1.1% of section data
MD5 363d04a82a4f34e1bc46f3b761049be2

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