📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes. The attack leveraged known flaws in GitHub Actions workflows and trust boundaries, illustrating how public research can be weaponized rapidly.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise multiple TanStack npm packages within six minutes, using GitHub Actions and trust boundary breaches. This incident underscores how known security flaws can be rapidly weaponized in supply-chain attacks, even against security-conscious organizations.
The attack involved the creation of a malicious fork of the TanStack/router repository by a threat actor, who then inserted a crafted commit. The attacker used a forged identity and manipulated the pull request process to trigger malicious workflows. The attack leveraged three known vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across fork boundaries, and extraction of OIDC tokens from runner memory. These vulnerabilities, each documented in public security research before 2026, were chained together to breach trust boundaries and gain write access to npm packages.
Crucially, no npm tokens were stolen, and the npm publish workflow was not directly compromised. Instead, the attacker minted an in-memory OIDC token and exfiltrated credentials via an encrypted messaging network, demonstrating advanced tradecraft. The incident was detected 28 hours after the initial fork creation, with forensic analysis confirming the chain of vulnerabilities was necessary for the breach. The attack is part of a broader wave of supply-chain compromises affecting over 160 packages, including those from Mistral AI, UiPath, and others, in what security researchers call the Mini Shai-Hulud campaign.
Three public vulnerabilities.
Chained.
The TanStack npm compromise of May 11, 2026 — published research recombined into working tradecraft, weaponized faster than defenders deploy mitigations.
84 malicious versions across 42 packages. Six-minute publish window. No npm tokens stolen. OIDC minted in memory and exfiltrated via Session Protocol. Three vulnerabilities chained — each documented in public research 12-24 months before the attack. Same date as the GTIG zero-day disclosure. The composition is the attack surface.
Each bridges the trust boundary the others assumed.
PR fork code crossing into base-repo cache. Base-repo cache crossing into release-workflow runtime. Release-workflow runtime crossing into npm registry write access. The composition only works because each vulnerability bridges the trust boundary the others assumed.
pull_request_target for fork PRs and checked out the fork’s PR-merge ref to run a build. Bypasses first-time-contributor approval gate. Author attempted trust split but missed that actions/cache@v5‘s post-job save is not gated by permissions:. Cache scope is per-repo, shared across triggers.Linux-pnpm-store-${hashFiles('**/pnpm-lock.yaml')} — exact match. actions/cache@v5 post-step saves poisoned store to that key. Restored entirely as designed when release.yml next runs on push to main.id-token: write for legitimate npm OIDC trusted publishing. Poisoned cache invokes attacker binaries: locate Runner.Worker via /proc/*/cmdline, dump memory via /proc//maps + /proc//mem , extract OIDC token, POST to registry.npmjs.org. Bypasses workflow’s Publish Packages step entirely.The attacker did not invent novel tradecraft. They recombined published research. Verbatim Python script — attribution comment preserved — from the March 2025 tj-actions disclosure. Every defensive research publication becomes attacker reference material within 12-24 months.
IoT Supply Chain Security Risk Analysis and Mitigation: Modeling, Computations, and Software Tools (SpringerBriefs in Computer Science)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
May 10 17:16 fork. May 11 19:50 detection.
From the attacker creating a renamed fork (deliberately evading fork-list searches) through the cache poisoning phase, the detonation phase, and the rapid external detection by Ashish Kurmi at StepSecurity. The TanStack postmortem published the complete root cause analysis publicly within hours.
PHASE
65bf499d authored by fabricated identity claude (NOT real Anthropic Claude). [skip ci] prefix suppresses CI on push. Adds packages/history/vite_setup.mjs — ~30,000-line bundled JS payload.PREP
pull_request_target. No first-time-contributor approval — pull_request_target bypasses that gate. pr.yml blocked.TRIGGER
65bf499d on PR head. bundle-size.yml’s benchmark-pr job checks out refs/pull/7378/merge, runs pnpm install + pnpm nx run @benchmarks/bundle-size:build. Executes fork-controlled vite_setup.mjs.EXEC
Linux-pnpm-store-6f9233a50def742c09fde54f56553d6b449a535adf87d4083690539f49ae4da11 (1.1 GB) saved for TanStack/router, scoped to refs/heads/main. Keyed to match what release.yml will compute on next push.ACTIVE
b1c061af). Visible PR diff is 0-file no-op. PR closed and branch deleted in same minute. Cache poison persists. PR appears benign in retrospective review./proc/*/cmdline, dumps memory, extracts OIDC token, POSTs to registry.npmjs.org. Bypasses defined Publish Packages step entirely.EXEC
@tanstack/history@1.161.12 etc. Six minutes between the two publish waves. Workflow status: failure (tests broke; publish still happened).BLAST
DETECTION
COMPLETE
DevOps with GitHub Actions: A Practical Guide to Building Secure, Scalable, and Production-Ready CI/CD Automation Pipelines
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
160+ packages. One worm. Same threat actor.
The TanStack compromise is one node in the broader Mini Shai-Hulud campaign by threat group TeamPCP — the same actor behind LiteLLM PyPI (March 2026), Bitwarden CLI npm, SAP CAP npm, and Lightning PyPI (April 30, 2026). Self-propagating worm pattern. First documented npm worm with valid SLSA Build Level 3 attestations.
May 2026 wave
weekly downloads
compromised May 12
fork → detection
registry.npmjs.org/-/v1/search?text=maintainer: → republish with same injection. Active operational campaign as of May 12, 2026.npm package vulnerability scanner
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
IOCs · copy-pasteable for hunting queries.
The TanStack postmortem published comprehensive IOCs. Defenders should hunt for these across their environments. The attacker forged a “claude” identity using claude@users.noreply.github.com — not the real Anthropic Claude Code GitHub App. This identity-confusion tactic deserves specific attention in git-log audits.
bun run tanstack_runner.js && exit 1 on install — payload runs, then optional dep “fails” gracefully.router_init.js (~2.3 MB, package root, not in files array). Also: tanstack_runner.js per Socket analysis.https://litter.catbox.moe/h8nc9u.js, https://litter.catbox.moe/7rrc6l.mjs. Secondary exfil via legitimate-looking GitHub GraphQL API traffic.git log --all --author=claude@users.noreply.github.com across all repos. Force-push revert if found.zblgg (id 127806521) · voicproducoes (id 269549300 · account created 2026-03-19 — fresh account, public repos named “A Mini Shai-Hulud has Appeared”). Attacker fork: github.com/zblgg/configuration (renamed). Workflow runs: 25613093674 · 25691781302.
Incident Response Team Mug – Cybersecurity Alert Design – 11 oz Ceramic
CYBERSECURITY DESIGN: Features bold 'Incident Response Team' typography surrounded by alert symbols, shield icons, padlocks, and intricate circuit…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Installed it? Rotate. Maintain packages? Audit.
Three response tracks. If you installed an affected version on May 11: treat your host as compromised. If you maintain OSS with similar workflow patterns: audit pull_request_target immediately. If you consume the npm ecosystem at enterprise scale: deploy install-time monitoring and lockfile pinning.
- Rotate AWS, GCP, Azure, Kubernetes service-account tokens, Vault tokens, npm
~/.npmrc, GitHub tokens, SSH private keys - Review GitHub Actions runs after 2026-05-11T19:20Z for unexpected npm publish events
- Check outbound connections to
filev2.getsession.org·seed*.getsession.org - Check downstream propagation — if your packages were published during a CI run that installed compromised version, those may also be compromised
- Audit
~/.claude/+.vscode/tasks.json· removerouter_runtime.js,setup.mjs git log --all --author=claude@users.noreply.github.com· revert if found- Run
npm token list· revoke unrecognized tokens
- Audit pull_request_target workflows immediately · never check out fork-submitted code without explicit approval gates
- Pin third-party action refs to commit SHAs ·
actions/checkout@8e5e7e5ab8...not@v6 - Separate cache scopes for trusted vs untrusted contexts · explicit
restore-keysandkeypatterns - Consider moving from OIDC trusted publisher to short-lived classic tokens with manual review
- Add internal alerting on npm publishes · fire on any publish that doesn’t originate from expected workflow step
- Audit other repos for the same bundle-size.yml-style pattern
- Restrict
id-token: writeto only the publish step that needs it
- Deploy npm package monitoring at install time · Socket / StepSecurity / Snyk · Socket flagged TanStack in 6 minutes
- Lockfile-pinned dependencies don’t auto-pull new versions · only consumers installing during the publish window were affected
- Audit lockfiles for
github:URLoptionalDependencies· unusual for production deps, exact pattern used here - CI/CD secret rotation automation · 30-90 day schedule regardless of incident status
- Treat provenance attestations as one layer, not sole verification · Mini Shai-Hulud produces valid Build L3 attestations on malicious packages
- Establish IR playbooks for OSS supply-chain compromise scenarios
Three pieces of public security research. Twelve months between the latest and the attack. Zero novel attacker tradecraft. A competent maintainer team with 2FA and OIDC trusted publishing — compromised through a chain that no individual vulnerability in their stack would have enabled. The composition is the attack surface.
Implications of Public Research in Rapid Supply-Chain Attacks
This incident demonstrates that publicly available security research can be rapidly weaponized by adversaries to execute sophisticated supply-chain attacks. The fact that each vulnerability was previously documented but not yet mitigated highlights a critical gap in defense deployment speed. The attack’s reliance on chaining known flaws underscores the need for faster adoption of mitigations and improved security practices in open-source and enterprise ecosystems. It also signals a shift where attacker tradecraft increasingly mirrors published research, reducing the novelty but increasing the threat’s immediacy.
Pre-Existing Vulnerabilities and the 2026 Supply-Chain Wave
The attack exploited three vulnerabilities publicly documented between March 2025 and May 2024: the pull_request_target “Pwn Request” pattern (GitHub Security Lab), cache poisoning across fork boundaries (Adnan Khan, May 2024), and OIDC token extraction from runner memory (StepSecurity, March 2025). These findings outlined ways malicious actors could cross trust boundaries within CI/CD pipelines, manipulate build artifacts, and exfiltrate credentials. The May 11, 2026 incident exemplifies how these vulnerabilities, each known for over a year, can be combined into a potent attack chain. This event is part of a broader supply-chain compromise wave affecting over 160 packages, illustrating systemic risks in open-source ecosystems.
“The TanStack incident exemplifies how publicly documented vulnerabilities can be combined into sophisticated attack chains that outpace defensive mitigation deployment.”
— Thorsten Meyer
Remaining Unknowns About the Attack Chain and Impact
While forensic analysis confirms the chain of vulnerabilities was exploited, details about the full extent of exfiltrated data or potential further compromises remain unclear. The precise operational steps taken after the initial breach are still under investigation, and whether other packages or ecosystems have been similarly targeted is not yet confirmed. The speed at which defenders can deploy mitigations against such chained vulnerabilities is also uncertain, emphasizing ongoing operational challenges.
Future Mitigations and Defensive Strategies Post-Incident
Security teams are expected to prioritize patching and mitigating known vulnerabilities in CI/CD pipelines, especially those related to trust boundary crossings. Increased monitoring of fork activity, stricter controls on pull request workflows, and faster deployment of security updates are likely to be emphasized. Industry experts will also advocate for improved detection of in-memory token exfiltration and better vetting of third-party dependencies. The incident underscores the urgency for the ecosystem to accelerate mitigation deployment and adopt more resilient security architectures.
Key Questions
How did the attacker exploit the vulnerabilities in TanStack?
The attacker created a malicious fork, inserted a crafted commit, and triggered workflows that exploited trust boundary vulnerabilities to exfiltrate credentials and compromise package publishing processes.
Were any tokens or credentials stolen during the attack?
No npm tokens were stolen; instead, the attacker minted an in-memory OIDC token and exfiltrated credentials via an encrypted messaging protocol.
What vulnerabilities were chained in this attack?
The attack chained three known vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across fork boundaries, and OIDC token extraction from runner memory.
What does this incident mean for open-source security?
It highlights the need for faster mitigation deployment, better trust boundary controls, and increased awareness of how published research can be weaponized rapidly.
Source: ThorstenMeyerAI.com
