Malicious Base64 Decoded Shell Payload Execution

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-11-01
Updated
2026-11-01

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects a base64-decoded command being piped directly into a shell, the second-stage delivery pattern seen after Log4Shell LDAP/JNDI exploitation. Post-exploitation payloads decode an encoded command with base64 -d and pipe it to bash to fetch and run miner or botnet droppers while evading plaintext detection.

Related detections9 linkedT1140 — drag to rearrange
Suspicious Bash Decode Chain Using curl xxd and base64 Piped to eval via Linux Shell
Suspicious Base64 Decoded Payload Piped to Shell on Linux
Suspicious Base64 Decoding Piped to Shell on macOS
Suspicious Hex Decoding Piped to Shell via xxd on macOS
Malicious Shell Payload Piped from curl to zsh
Obfuscated Base64-Decoded Payload Piped to a Shell (via process_creation)
Obfuscated Base64-Decoded Payload Piped to Shell via macOS ClickFix Terminal Lure (via process_creation)
Suspicious awk Character Generation Piped to Shell on VMware ESXi (via process_creation)
Suspicious certutil Decode or Remote Download
Malicious Base64 Decoded Shell Payload Execution
Pivot detection · T1140 · 9 related

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