Linux SSHD Logs: Suspicious OpenSSH Daemon Error Keywords

Alerts on sshd log entries with specific OpenSSH fatal or cryptographic error messages indicating suspicious access attempts.

FreeReviewedSigma · Medium · v3
Product
linux
Service
sshd
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-06-30
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches specific OpenSSH/sshd error text patterns in Linux SSHD logs that indicate unexpected, fatal, cryptographic, or malformed-input failures. Such messages can occur when an attacker attempts to exploit SSH protocol parsing or crypto handling behavior. It relies on the presence of these exact error keywords in sshd service logs.

Related detections9 linkedT1190 — drag to rearrange
Suspicious Telerik UI RadAsyncUpload Request Indicating CVE-2019-18935 Exploitation (via webserver)
Malicious IIS Worker Process Spawning Shell for Out-of-Band Interaction via Command Line
Malicious wp2shell WordPress Exploitation via Batch Endpoint User Agent
Suspicious TOLLBOOTH Webshell URI Access
Suspicious ffuf Fuzzing Requests Against Web Server
Suspicious AI Agent Compromise via Web Worker Spawning Shell or Network Tool
Malicious wp2shell WordPress RCE via Web Server Spawning Shell Recon
Suspicious Child Process Spawned by IIS Worker Process w3wp
Possible Log4Shell Exploitation via Java Spawning Shell or Download Utility
Linux SSHD Logs: Suspicious OpenSSH Daemon Error Keywords
Pivot detection · T1190 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.