Malicious Node.js Execution of test.js from .vscode Folder in Lazarus Lure (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-14
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 the Node.js runtime running a script named test.js located inside a .vscode project folder, the exact loader pattern used by the Lazarus BeaverTail campaign after a victim runs npm install. The hidden .vscode directory disguises the malicious bootstrap among normal editor files. This execution kicks off the download of the follow-on Python infostealer.

Related detections9 linkedT1204.002 — drag to rearrange
Malicious Silent AteraAgent RMM Installation via IntegratorLogin
Suspicious Windows Script Host Execution of JavaScript from Temporary Archive Extraction Folder (via process_creation)
Suspicious PowerShell Launched by MSIX StartingScriptWrapper From WindowsApps via Process Creation (via process_creation)
Suspicious PowerShell Remote TXT Payload Download Spawned by Shortcut via LNK (via process_creation)
Suspicious Script Interpreter Spawned by OneNote via Embedded Attachment (via process_creation)
Suspicious ClickFix Command Execution via RunMRU Registry Key
Suspicious Base64 Bash Execution via nohup on macOS via ClickFix (via process_creation)
Suspicious PowerShell Download Spawned From Explorer via ClickFix (via process_creation)
Suspicious Lampion ClickFix PowerShell Download and Execute via Run Dialog
Malicious Node.js Execution of test.js from .vscode Folder in Lazarus Lure (via process_creation)
Pivot detection · T1204.002 · 9 related

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