Linux Process Creation: Shell Command Piped Into Another Shell

Flags Linux processes that start with sh/bash -c and pipe execution into a subsequent shell.

FreeReviewedSigma · Medium · v2
Product
linux
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-14
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Linux processes whose command line begins with a shell wrapper (sh -c or bash -c) and includes piping that results in execution by another shell. Attackers commonly use this chaining to execute staged commands while preserving interactive or script-driven behavior across multiple shells. The detection relies on process creation telemetry capturing the full CommandLine for the spawned process.

Related detections9 linkedT1140 — drag to rearrange
Suspicious Bash Decode Chain Using curl xxd and base64 Piped to eval via Linux Shell
Suspicious lwp-download Retrieval of Remote File Masquerading as Image via 8220 Gang
Malicious PolarEdge QNAP Backdoor Dropper Script in Temp (via file_event)
Suspicious PowerShell Payload Extraction from PNG Polyglot via findstr
Suspicious Python Inline Deobfuscation and Execution One-Liner
Suspicious Base64 Decoded Payload Piped to Shell on Linux
Suspicious Remote File Download via certutil URLCache (via process_creation)
Malicious certutil Decodehex Payload Reconstruction by DarkGate
Suspicious StrelaStealer Base64 Payload Decode via Certutil (via process_creation)
Linux Process Creation: Shell Command Piped Into Another Shell
Pivot detection · T1140 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.