Malicious Child Process Spawned From n8n Node Process

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-10-05
Updated
2026-10-05

ATT&CK techniques

Initial Access → Discovery
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects a Node.js process running n8n spawning shell, discovery or downloader child processes such as sh, whoami, wget or curl, the exploitation behavior of the Zerobot botnet abusing the CVE-2025-68613 expression sandbox escape. The n8n workflow engine should not launch system commands, so these child spawns indicate remote code execution with n8n process privileges. This pattern reflects active post-exploitation on the host.

Related detections9 linkedT1059.004 — drag to rearrange
Malicious Next.js Node Process Spawning Shell Downloader after RSC Deserialization RCE (via process_creation)
Possible OMIGOD Unauthenticated OMI WSMan Command Execution via Web Request (via webserver)
Suspicious Java Process Spawning Download or Shell Utility (Exposed JDWP Abuse)
Suspicious PostgreSQL Spawning Command Shell via COPY FROM PROGRAM (Soco404)
Possible CUPS cups-browsed Remote Code Execution via Shell Child Process
Possible TP-Link Command Injection via WlanNetworkRpm Endpoint (via webserver)
Malicious Command Injection Probe via node Spawning Shell Arithmetic Echo (via process_creation)
Malicious Reverse Shell via bash dev tcp Redirection (via process_creation)
Suspicious GeoServer Java Process Spawning Download Utility
Malicious Child Process Spawned From n8n Node Process
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.