telexed ~ c / 88b90fa3-19fradar:60 · otherLIVE
← back
NO.
#88b90fa3
Topic
OTHER
Source
GeekNews
Published
2026-05-12 00:52:26
Importance
★ 6/10 — radar 60
Postmortem: `TanStack` npm Supply-Chain Breach
FIG-0881:1

Postmortem: `TanStack` npm Supply-Chain Breach

A six-minute CI-to-publish compromise turned pull_request_target, cache poisoning, and stolen OIDC credentials into malicious npm releases. If your stack pulls @tanstack/*, treat GitHub Actions hardening and dependency pinning as urgent hygiene, not optional.

[ KEY POINTS ]
  1. The blast radius was 42 @tanstack/ packages and 84 malicious versions published within 6 minutes; short windows still break CI fast.
  2. The chain combined pull_request_target, GitHub Actions cache poisoning, and OIDC token extraction from runner memory; one weak workflow can reach package publishing.
  3. Stolen npm publish access means trusted frontend dependencies become an attack path; lockfiles alone do not save you after a poisoned release.
  4. This pushes routine defenses up the priority list: tighter GitHub Actions permissions, cache isolation, and faster dependency incident response.
Originalnews.hada.io/topic?id=29413Read original →

// related