GridinSoft Threat Intelligence

libssl-1_1.dll file report

Under review File reputation report
MD5 311a39a0b96b93ea87f98633997be72f
Latest seen 2021-02-08 04:09:59 (5 years ago)
First seen 2019-09-02 17:23:29 (6 years ago)
Size 625 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-09-02 17:23:29 (6 years ago); latest analysis 2021-02-08 04:09:59 (5 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.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 2021-02-08 04:09:59 (5 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: 311a39a0b96b93ea87f98633997be72f
Size: 625 KB
First Published: 2019-09-02 17:23:29 (6 years ago)
Latest Published: 2021-02-08 04:09:59 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-08 04:09:59 (5 years ago)
%programfiles%
%programfiles%\totalav\updates
%commonappdata%\totalav\updates\5_5_83

ThreatInfo has observed libssl-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 81.4%
Windows 7 13.5%
Windows 8.1 3.3%
Windows 8 0.9%
Windows Server 2016 0.9%

The most common operating system signal for libssl-1_1.dll is Windows 10 with 81.4% 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.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 0x00058baf
Image base 0x10000000

PE Sections:

Sections 6
Raw data 639488

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

.text 461824 bytes · 72.2% of section data
MD5 0ac6ea8d5dcdc3518987436508a94b9c
.rdata 118784 bytes · 18.6% of section data
MD5 60761a7e2c58169d56928b006521072f
.data 19968 bytes · 3.1% of section data
MD5 8b1cfb1a5ffc84be58d5ad2d0cadc101
.idata 16896 bytes · 2.6% of section data
MD5 10a6188b2674400b960e608c546a8405
.rsrc 2048 bytes · 0.3% of section data
MD5 3b115f146b164f5a5795f8718c825e31
.reloc 19968 bytes · 3.1% of section data
MD5 47c5da72b74ac0a13c70deeda686e790

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 311a39a0b96b93ea87f98633997be72f.
  • 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.