Suspicious Inline node.exe Command Executing Network and Process Spawning Code

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-08-27
Updated
2026-08-28

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 node.exe invoked with inline evaluated code that references network, command execution, and filesystem modules such as http, execSync, spawn, fs, and zlib. Microsoft attributed this pattern to Node.js malware that downloads and runs additional payloads directly from the command line. Inline module chaining lets the attacker fetch and execute code without dropping a script file, making it a strong indicator of malicious activity.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Deno Runtime Execution of Remote JavaScript Payload (via process_creation)
Windows: Deno writes files from remote HTTPS content into AppData
macOS: In-Memory Download and Compile via curl and osacompile in a Single Command
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Suspicious Remote HTA Payload Execution via MSHTA
Possible PurpleFox MSHTA to Msiexec Remote MSI Chain
Suspicious Node.js Script Execution from AppData Roaming
Antivirus Check and Remote Loader Retrieval in LNK Command Chain
Suspicious PowerShell Hidden Web Download via Invoke-WebRequest by CatB Ransomware
Suspicious Inline node.exe Command Executing Network and Process Spawning Code
Pivot detection · T1105 · 9 related

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