Malicious Next.js Node Process Spawning Shell Downloader after RSC Deserialization RCE (via process_creation)

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

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects a Node.js process spawning a shell that fetches a remote payload with wget or curl or a dev tcp socket, the post-exploitation behavior following React2Shell CVE-2025-55182 deserialization RCE in Next.js. Adversaries leverage the compromised Node runtime to pull down Mirai and dropper payloads onto the server.

Related detections9 linkedT1059.004 — drag to rearrange
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
Possible Shellshock Bash Function Definition Injection via Process Creation
Malicious Next.js Node Process Spawning Shell Downloader after RSC Deserialization RCE (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.