Linux File Creation Indicators for TanStack Runner and Persistence Components

Alerts on creation of TanStack-style runner/persistence filenames on Linux, including .claude/.vscode router_runtime.js and /tmp/transformers.pyz.

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

ATT&CK techniques

Initial Access → Priv Esc
  1. Recon

  2. Resource Dev

  3. Defense Evasion

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags Linux file creation events where the target filename ends with specific JavaScript runner and persistence component paths (including router_init.js and tanstack_runner.js) or matches a transformer payload path (/tmp/transformers.pyz). Such artifacts can indicate supply-chain compromise staging, where malicious scripts are dropped and persistence scaffolding is created under hidden directories. It relies on file-event telemetry that includes the created file path or target filename to match the defined suffix/path patterns.

Related detections9 linkedT1059.007 — 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)
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 Child Process Spawned by Python Interpreter via Process Creation
Suspicious Script Host Execution of Decoy-Named JavaScript Dropper (PS1Bot)
Linux File Creation Indicators for TanStack Runner and Persistence Components
Pivot detection · T1059.007 · 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.