📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
In May 2026, attackers exploited a chain of three publicly documented vulnerabilities to breach TanStack npm packages. The attack leveraged known security flaws, highlighting the speed at which public research can be weaponized. The incident underscores the need for faster defensive responses in supply-chain security.
On May 11, 2026, an attacker exploited a chain of three publicly known vulnerabilities to compromise multiple TanStack npm packages within six minutes. This incident, confirmed by security researchers and the TanStack team, highlights how publicly available research can be rapidly weaponized to breach supply chains, even by security-conscious organizations. The attack’s speed and complexity demonstrate the evolving threat landscape for open-source ecosystems.
The attack involved a coordinated exploitation of three vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from GitHub Actions runners. Each vulnerability had been publicly documented prior to the incident, with the earliest research published in March 2025. The attacker created a malicious fork of TanStack/router on May 10, then used a fabricated commit and a malicious pull request to trigger the chain of exploits.
Specifically, the attacker used a forged identity to add malicious code in the fork, which was then merged via a pull request targeting the main repository. The malicious code exploited the cache poisoning vulnerability to cross trust boundaries, ultimately allowing the attacker to mint an OIDC token in memory. This token was exfiltrated through the Session Protocol, a secure messaging network, without theft of npm tokens or compromise of the publish workflow. The attack was detected 28 hours after the initial fork, with forensic analysis confirming the chain of vulnerabilities was necessary for success.
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
npm package vulnerability scanner
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.
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.
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.
Klein Tools 80093 Cable Tester, VDV LAN Kit with LAN Tester, Pass Thru Crimper, CAT6/CAT5e Plugs and Strain Relief Boots, 5-Piece
SMART BUY: A complete, high-performance kit that offers convenience and value
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 Vulnerability Exploitation in Supply Chains
This incident underscores that publicly documented security flaws, once known, can be rapidly combined and weaponized by attackers, often outpacing defenders’ mitigation efforts. The attack demonstrates that even security-conscious open-source projects with multi-factor authentication and trusted publishing mechanisms remain vulnerable when vulnerabilities are chained together. It highlights the urgent need for faster deployment of mitigations and continuous monitoring in supply-chain security, especially as AI-augmented attack techniques evolve.
The Broader 2026 Supply-Chain Security Landscape
The May 2026 attack on TanStack is part of a larger wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. Prior to this, research published over the past year detailed vulnerabilities such as GitHub Actions cache poisoning (May 2024), OIDC token extraction (March 2025), and the dangerous pull_request_target pattern. These publicly available findings created a pool of attacker tradecraft that was exploited in the TanStack incident, illustrating the speed at which open-source security research can be weaponized.
“The TanStack incident exemplifies how publicly available research can be rapidly assembled into effective attack chains, surpassing the pace of defensive mitigation deployment.”
— Thorsten Meyer, security researcher
Remaining Unknowns About Attack Scope and Impact
Details about the full extent of the compromised packages and any potential downstream impacts are still emerging. It is not yet clear whether additional repositories or packages were affected beyond the publicly identified ones, or if there are undisclosed malicious payloads. The precise timeline of attacker actions within the 28-hour window remains under investigation, and the full operational tradecraft used in the attack may be more extensive than currently documented.
Next Steps for Defense and Industry Response
Security teams are expected to review and strengthen trust boundary protections, especially concerning pull request workflows, cache management, and token handling. Industry-wide, there will likely be increased emphasis on rapid deployment of mitigations for publicly documented vulnerabilities, along with enhanced monitoring for chain exploits. Ongoing forensic analysis aims to clarify the full scope of the breach, while developers and maintainers are urged to adopt more conservative security controls and review their CI/CD pipelines for similar chain vulnerabilities.
Key Questions
How did the attacker exploit known vulnerabilities so quickly?
The attacker combined publicly documented vulnerabilities—each necessary but not sufficient alone—into a chain that allowed them to cross trust boundaries and exfiltrate tokens, all within a six-minute window on May 11, 2026.
Were npm tokens stolen during the attack?
No, the attacker minted an OIDC token in memory and exfiltrated credentials via the Session Protocol without stealing npm tokens or compromising the publish workflow.
What are the main vulnerabilities involved in this attack?
The attack relied on three publicly known vulnerabilities: the pull_request_target pattern, cache poisoning across trust boundaries, and OIDC token extraction from GitHub Actions runners.
Can such attacks be prevented in the future?
Mitigations include stricter controls on pull request workflows, better isolation of cache and runtime environments, and faster deployment of patches for known vulnerabilities. However, chaining of multiple vulnerabilities remains a significant challenge.
Source: ThorstenMeyerAI.com
