📊 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. The attack used publicly known flaws in GitHub Actions and trust boundaries, illustrating how attacker tradecraft now combines published research faster than defenses can adapt.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages, using a combination of social engineering, trust boundary breaches, and memory extraction techniques. This incident underscores how publicly available research can be weaponized in rapid, complex attacks, posing a significant challenge for software supply chain security.
The attack began on May 10 when the attacker created a malicious fork of the TanStack/router repository, deliberately renamed to evade detection. The attacker then committed a payload containing a large JavaScript bundle, using forged identities to mask their activity. On May 11, the attacker opened a pull request that triggered GitHub Actions workflows configured with pull_request_target, a known vulnerable pattern. Through this chain, the attacker was able to exfiltrate an OIDC token in memory from the GitHub Actions runner, which they used to authenticate and publish malicious package versions to npm within six minutes. The attack relied on three previously documented vulnerabilities: the pull_request_target ‘Pwn Request’ pattern, cache poisoning across fork and base trust boundaries, and OIDC token extraction from runner memory. Each vulnerability alone was insufficient; together, they created a pathway for the breach. The incident was detected within 28 hours, and extensive forensic analysis confirmed the chain of 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.
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
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.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.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 the Chain-Linked Supply Chain Attack
This incident demonstrates how publicly available security research can be rapidly weaponized, surpassing the pace at which defenders deploy mitigations. It highlights the importance of understanding trust boundaries in CI/CD pipelines and the need for more resilient security architectures. For open-source maintainers and enterprise users, the attack underscores the risk posed by complex chains of known vulnerabilities, especially when combined with attacker tradecraft that exploits trust relationships. The incident also reflects a broader trend in 2026, where AI-augmented attack techniques accelerate the exploitation of known vulnerabilities, making traditional defense strategies less effective.
Broader Trends in 2026 Supply-Chain Attacks and Research Exploitation
The TanStack incident is part of a wave of supply chain compromises in May 2026, with over 160 packages affected across multiple organizations, including Mistral AI and UiPath. The attack was facilitated by publicly documented vulnerabilities, such as cache poisoning (May 2024), OIDC token extraction (March 2025), and the dangerous use of pull_request_target workflows. These vulnerabilities, all known for over a year, were combined into a single attack chain, demonstrating how the attack surface has expanded through the accumulation of publicly available research. The incident coincides with the disclosure of the first AI-built zero-day by Google Threat Intelligence Group, illustrating a convergence of offensive AI and public research that is reshaping the threat landscape.
“The TanStack attack exemplifies how publicly documented vulnerabilities, when chained together, can be weaponized faster than defenders can respond, especially in an AI-augmented threat environment.”
— Thorsten Meyer
Remaining Uncertainties About the Attack Chain and Mitigations
While the forensic analysis confirms the chain of vulnerabilities exploited, it remains unclear how widespread the attack’s impact is beyond TanStack packages or whether additional, undisclosed vulnerabilities were also leveraged. The full extent of attacker access and whether other repositories or ecosystems are similarly compromised are still under investigation. Additionally, the effectiveness of current mitigations against future chained attacks using publicly documented vulnerabilities is uncertain, given the rapid pace of AI-augmented attack development.
Future Steps for Defense and Monitoring of Supply Chain Risks
Organizations should review their CI/CD workflows for similar trust boundary vulnerabilities, especially those involving pull_request_target, cache management, and token extraction. Enhanced monitoring for malicious activity in open-source repositories and automated detection of suspicious commits or PRs are recommended. Security teams are also likely to push for more resilient pipeline architectures and stricter access controls. The incident underscores the need for ongoing research, proactive threat modeling, and faster deployment of mitigations to keep pace with attacker innovations.
Key Questions
What are the main vulnerabilities exploited in the TanStack attack?
The attack chained three publicly documented vulnerabilities: the pull_request_target ‘Pwn Request’ pattern, cache poisoning across trust boundaries, and OIDC token extraction from GitHub Actions runner memory.
How did the attacker exfiltrate credentials without stealing npm tokens?
The attacker minted an OIDC token in memory during the workflow execution and exfiltrated it via the encrypted Session Protocol, avoiding the need to steal stored tokens.
What does this incident imply for open-source maintainers?
It highlights the importance of understanding trust boundaries, avoiding risky workflow patterns, and implementing stricter security controls to prevent chained exploits based on publicly known vulnerabilities.
Are these vulnerabilities still exploitable today?
While mitigations exist, the attack demonstrates how chains of known vulnerabilities can be combined in novel ways. Continuous review and improved security practices are necessary to reduce risk.
What lessons does this incident offer for enterprise security teams?
Security teams should prioritize holistic security approaches, monitor for chain exploits, and stay informed about public research that could be weaponized in future attacks.
Source: ThorstenMeyerAI.com
