📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
An attacker exploited three chained vulnerabilities, all previously documented in public security research, to compromise TanStack npm packages. The attack highlights how public research can be weaponized faster than defenses can respond.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages, using sophisticated techniques that bypassed standard security measures. This incident underscores the increasing speed at which threat actors weaponize publicly available research, making traditional defenses insufficient against fast-moving supply chain attacks.
The attack was carried out through a series of chained vulnerabilities that each individually were known and documented before 2026. The attacker created a malicious fork of the TanStack/router repository, inserted a crafted commit, and used GitHub Actions workflows with the pull_request_target pattern to inject malicious code into the release process. The attacker then minted an OIDC token in memory, exfiltrating credentials via the Session Protocol, without stealing npm tokens or compromising the npm publish workflow directly.
Key vulnerabilities involved include the pull_request_target ‘Pwn Request’ pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory. All three were necessary for the attack, and each had been publicly researched and documented before the incident, with the latest being March 2025.
Despite the TanStack team’s security measures, including 2FA and trusted publishing, the chain of vulnerabilities allowed the attacker to bypass protections, demonstrating how the attack surface is now composed of publicly known flaws that can be combined for high-impact exploits.
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.
Software Supply Chain Defense: Securing Build Environments, Toolchains, and CI/CD Infrastructure Against Advanced Threats
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.OIDC token security tools
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.npm package vulnerability scanner
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-Driven Supply Chain Attacks
This incident exemplifies how publicly available security research can be rapidly weaponized by attackers, outpacing defenders’ ability to deploy mitigations. It highlights the need for the open-source ecosystem and enterprise developers to re-evaluate trust boundaries, especially in CI/CD pipelines, and to develop faster, more integrated defense strategies against such chained vulnerabilities.
The attack also underscores the broader trend of increasing sophistication in supply chain compromises, where the attack surface is no longer limited to zero-day exploits but includes the strategic combination of known weaknesses. This shift demands a reevaluation of security practices at both the technical and operational levels.
Public Research and the Evolution of Supply Chain Attacks in 2026
Since 2024, multiple vulnerabilities affecting CI/CD workflows and trust boundaries have been publicly documented, including GitHub Actions cache poisoning (May 2024) and OIDC token extraction (March 2025). These findings laid the groundwork for the May 11, 2026, TanStack attack, which combined these known flaws into a sophisticated chain. The incident occurs amid a broader wave of supply chain compromises affecting over 160 packages, part of the ongoing Mini Shai-Hulud campaign, illustrating the systemic risks posed by publicly known vulnerabilities when weaponized at scale.
The confluence of these research findings and the attack demonstrates how attacker tradecraft can compress what was once considered separate technical issues into a single, high-impact exploit, emphasizing the urgency for the community to accelerate mitigation deployment.
“The TanStack incident is a clear example of how publicly documented vulnerabilities can be combined into a powerful attack chain that outpaces traditional defense responses.”
— Thorsten Meyer, security researcher
Unclear Aspects of the Ongoing Investigation
Details remain emerging regarding the full extent of the compromise, including whether other packages or repositories were affected beyond TanStack. The precise timeline of attacker actions within the compromised workflow is still under analysis, and the full operational scope of exfiltrated credentials via the Session Protocol has not yet been fully mapped.
It is also unclear how quickly the broader ecosystem will deploy mitigations against these chained vulnerabilities, and whether additional, undisclosed vulnerabilities may have been exploited.
Next Steps for Mitigation and Ecosystem Defense
Security teams and open-source maintainers are expected to prioritize patching workflows that rely on pull_request_target, implement stricter trust boundaries, and adopt faster response protocols for publicly documented vulnerabilities. Ongoing forensic analysis aims to identify any additional impacted packages and improve detection strategies.
Furthermore, industry-wide efforts are likely to accelerate, including updates to best practices for CI/CD pipeline security, enhanced monitoring for suspicious activity, and community sharing of threat intelligence to prevent similar chained attacks in the future.
Key Questions
How did the attacker exploit these vulnerabilities without stealing npm tokens?
The attacker minted an OIDC token in memory during the CI/CD process and exfiltrated credentials via the Session Protocol, a secure messaging network, avoiding the need to steal npm tokens or directly compromise the publish workflow.
Are other npm packages or repositories at risk from similar chained vulnerabilities?
Yes, given that the vulnerabilities exploited are publicly documented and affect common trust boundaries, other packages using similar workflows may be vulnerable if mitigations are not implemented promptly.
What can maintainers do to prevent similar attacks?
Maintainers should review and restrict the use of pull_request_target workflows, enforce stricter trust controls, and monitor for suspicious activity within their CI/CD pipelines, especially when leveraging public research findings.
How does this incident reflect broader trends in software supply chain security?
This attack exemplifies how publicly available security research can be rapidly combined into high-impact exploits, indicating a shift toward research-to-tradecraft compression and the need for faster, more integrated defensive measures.
Source: ThorstenMeyerAI.com
