Malicious Remote Script Piped Directly to a Shell (via process_creation)

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-09-04
Updated
2026-09-04

ATT&CK techniques

Execution → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule detects curl or wget output piped straight into sh or bash on Linux, a one-line download-and-execute pattern used to fetch and immediately run a remote payload. Piping a downloaded script to a shell is an ingress-and-execution technique tracked in the Red Canary Threat Detection Report. Detecting this chain surfaces remote code execution as it happens.

Related detections9 linkedT1059.004 — drag to rearrange
HamsaUpdate Linux Payload Download via Wget Piped to Bash (via process_creation)
Malicious Curl to Shell Dropper from Paste Site via Command Line
Malicious kagent RAT Delivery via HuggingFace Space Download (via process_creation)
Suspicious Remote Script Execution via curl Piped to bash with nohup on macOS (via process_creation)
Suspicious Botnet Payload Drop to Hidden Xdiag Temp Path
Malicious Remote Payload Piped to Shell via wget on PAN-OS
Suspicious Remote Script Downloaded via curl and Piped to Shell (via process_creation)
Suspicious File Download to tmp and Quarantine Removal via curl and xattr
Malicious macOS Payload Download and Execution via curl Piped to zsh
Malicious Remote Script Piped Directly to a Shell (via process_creation)
Pivot detection · T1059.004 · 9 related

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