Suspicious node.exe Inline Script Execution via -e

PremiumReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-18
Updated
2026-08-28

ATT&CK techniques

Execution
  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. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects node.exe executing an inline script through the -e flag, the stager execution method in the DEV#POPPER GitHub-lure infection. Victims who cloned the weaponized repository ran a hidden script that used node -e to bootstrap the RAT. While developers occasionally use node -e, inline Node execution from a cloned project should be reviewed for malicious staging.

Related detections9 linkedT1059.007 — drag to rearrange
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Suspicious Node.js Script Execution from AppData Roaming
Possible Reflected XSS via cPanel cpanelwebcall Endpoint CVE-2023-29489
SocGholish Fake Browser Update Script Execution (via process_creation)
Suspicious Contagious Interview Disk Enumeration via Node Spawning Wmic
Suspicious Inline node.exe Command Executing Network and Process Spawning Code
Suspicious NPM Install Hook Executing Setup Script via Node
Suspicious Script Host Spawning PowerShell Or Cmd via Gootloader
Suspicious Scheduled Task Executing JavaScript from Public Directory (via process_creation)
Suspicious node.exe Inline Script Execution via -e
Pivot detection · T1059.007 · 9 related

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