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
Suspicious PowerShell Spawned by Windows Script Host during Scarlet Goldfinch Infection (via process_creation)
Suspicious Windows Script Host Execution of JavaScript from Temporary Archive Extraction Folder (via process_creation)
Suspicious Whoami Discovery Spawned by Windows Script Host via Process Creation (via process_creation)
Suspicious Node.js Execution from User AppData Directory (via process_creation)
Malicious Shai-Hulud npm Worm Marker via SHA1HULUD Process Name (via process_creation)
Suspicious Script Host Downloader via MSXML and WScript Shell
Malicious VVS Discord Stealer Script Drop via injection-obf.js (via file_event)
Suspicious npm Postinstall node Execution of setup.cjs with Warnings Suppressed
Suspicious node.exe Executing Compiled JavaScript Bytecode File
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.