Linux Log Shellshock Expression Pattern Matching

Identifies Shellshock-style function-body expressions in Linux log data via keyword string matches.

FreeReviewedSigma · High · v3
Product
linux
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-03-14
Updated
2026-07-31

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  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 flags Shellshock-style function expression sequences appearing in Linux log files, including variations of (){:;}; and spaced variants. Such payload markers are used to trigger Bash function parsing behavior and can indicate attempted command injection. The detection relies on keyword matches in available text-based telemetry from Linux logging sources.

Related detections9 linkedT1505.003 — drag to rearrange
Suspicious Weaver Ant In-Memory Web Shell Marker in Web Request (via webserver)
Malicious Web Server Process Spawning Command Interpreter via Web Shell (via process_creation)
Malicious Web Shell Written to SharePoint LAYOUTS Directory by Worker Process (via file_event)
Malicious IIS Worker Process Spawning Command Shell for Webshell Reconnaissance (via process_creation)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious PHP Webshell Access with Hardcoded Key
Suspicious IIS Configuration Reconnaissance via Appcmd (via process_creation)
Malicious ManagementMailboxPicker Webshell Written by Diplomatic Specter
Malicious MOVEit human2 Webshell File Creation via file_event
Linux Log Shellshock Expression Pattern Matching
Pivot detection · T1505.003 · 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.