Malicious Shai-Hulud npm Worm Marker via SHA1HULUD Process Name (via process_creation)

PremiumReviewedSigma · High · v1
Category
process_creation
Author
HuntRule
Published
2026-10-20
Updated
2026-10-20

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 a process launched with the SHA1HULUD marker on its command line, the self-identifying tag used by the Shai-Hulud npm supply-chain worm. The worm spawns processes named SHA1HULUD during propagation and token theft, so this constant is a high-confidence indicator of compromise on developer and CI hosts.

Related detections9 linkedT1059.007 — drag to rearrange
Malicious Node.js Execution of Hidden .claude Setup Script
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)
Malicious Shai-Hulud npm Worm Marker via SHA1HULUD Process Name (via process_creation)
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.