Malicious Node.js Execution of Hidden .claude Setup Script

PremiumReviewedSigma · High · v1
Category
process_creation
Author
HuntRule
Published
2026-09-15
Updated
2026-09-15

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 Node.js executing a setup script from a hidden .claude directory, the auto-run payload delivered by the open source Shai-Hulud framework. A workspace tasks.json configured to run on folder open silently launches this script when a developer opens the repository. Node running a hidden .claude setup module is not part of normal project execution and marks the initial foothold.

Related detections9 linkedT1195.002 — drag to rearrange
Suspicious npm Postinstall Node Execution From Fixtures Path (BeaverTail OtterCookie)
Suspicious NPM Install Hook Executing Setup Script via Node
Malicious Bun Runtime Payload Dropped by Shai Hulud npm Supply Chain Attack
Malicious Shai-Hulud Bun Payload Execution via npm Preinstall Script (via process_creation)
Malicious Shai-Hulud npm Payload Execution via bun_environment Script (via process_creation)
Linux File Creation Indicators for TanStack Runner and Persistence Components
Windows TanStack Supply-Chain File Creation Indicators via router_init.js and router_runtime.js
Suspicious Node Payload Drop in Local Share Directory (via file_event)
Suspicious Node.js Spawning Script Interpreter for Dropped Payload
Malicious Node.js Execution of Hidden .claude Setup Script
Pivot detection · T1195.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.