Windows TanStack Supply-Chain File Creation Indicators via router_init.js and router_runtime.js

Alerts on Windows creation of router/tanstack runner and router_runtime files used in a TanStack supply-chain attack pattern.

FreeReviewedSigma · Medium · v5
Product
windows
Category
file_event
Author
Leonardo Gasparini (SigmaHQ), DRL 1.1
Published
2026-05-12
Updated
2026-07-31

ATT&CK techniques

Initial Access → Persistence
  1. Recon

  2. Resource Dev

  3. Priv Esc

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags Windows file creation events for specific JavaScript artifacts associated with a TanStack-related supply-chain compromise pattern. Attackers may drop or modify local runtime and initialization files to execute malicious code and establish persistence. The detection relies on file event telemetry, specifically the created target filename suffixes matching router_init.js and router_runtime.js under the expected paths.

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 Backdoored liblzma Loaded by sshd (CVE-2024-3094)
Malicious Shai-Hulud npm Payload Execution via bun_environment Script (via process_creation)
Linux File Creation Indicators for TanStack Runner and Persistence Components
Suspicious Node Payload Drop in Local Share Directory (via file_event)
Suspicious Child Process Spawned by Python Interpreter via Process Creation
Windows TanStack Supply-Chain File Creation Indicators via router_init.js and router_runtime.js
Pivot detection · T1195.002 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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