📊 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 public research and was executed within hours, highlighting the speed of offensive tradecraft in 2026.
On May 11, 2026, attackers exploited a chain of three previously documented vulnerabilities to compromise TanStack npm packages within a six-minute window, using public research to weaponize the vulnerabilities faster than defenses could respond. This incident underscores the increasing sophistication and speed of supply-chain attacks driven by AI-augmented attacker tradecraft.
The attack involved the publication of 84 malicious package versions across 42 TanStack npm packages, executed via a compromised GitHub Actions workflow. The attacker created a fake fork of the TanStack/router repository, injected malicious code through a crafted commit, and exploited three chained vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory. Each vulnerability was publicly documented before the attack, with the chain of exploits allowing the attacker to mint an in-memory OIDC token and exfiltrate credentials via an encrypted messaging network, without stealing npm tokens or compromising the publish workflow itself.
According to forensic analysis by TanStack and security researchers, the attack was facilitated by the attacker’s deliberate operational tradecraft, including renaming forks to evade detection and fabricating commit authorship. The incident is part of a broader wave of supply-chain compromises in May 2026, affecting over 160 packages across the ecosystem. The attack exemplifies how publicly available research can be rapidly weaponized, outpacing traditional mitigation efforts.
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
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.OIDC token security tools
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 Chained Vulnerabilities in Supply-Chain Attacks
This incident demonstrates that the most impactful supply-chain attacks in 2026 are no longer driven by novel technical exploits but by the rapid combination and deployment of publicly documented vulnerabilities. The attack on TanStack highlights how attacker tradecraft can leverage existing research to execute sophisticated operations faster than defenders can adapt, posing a serious threat to open-source ecosystems and enterprise supply chains alike.
Broader Trends in Supply-Chain Security and Public Research Exploitation
The May 2026 attack on TanStack is part of a larger wave of supply-chain compromises, including over 160 packages affected in a campaign linked to the Mini Shai-Hulud operation. The incident coincided with the disclosure of the first AI-built zero-day by Google Threat Intelligence Group, illustrating a broader trend where AI-augmented offensive techniques rapidly turn publicly available research into weaponized attack tools. Prior to this, security research had documented each of the three vulnerabilities used in the chain, making their combination a predictable yet highly effective attack vector. The attack underscores the challenge for defenders: published research becomes immediate tradecraft, and mitigation deployment lags behind adversaries’ rapid assembly of attack chains.
“The TanStack incident exemplifies how public research is being weaponized faster than the ecosystem’s defenses can respond, turning known vulnerabilities into sophisticated attack chains within hours.”
— Thorsten Meyer
Unresolved Questions About the Attack Chain and Mitigations
While forensic analysis has reconstructed the attack chain, it remains unclear how widespread the exploitation of similar chains might be across other projects. The extent of attacker access and whether additional victim packages are compromised are still under investigation. Furthermore, the effectiveness of current mitigations against such chained attacks, and how quickly defenders can adapt to prevent future incidents, remains uncertain.
Next Steps for Detection, Response, and Defense Improvements
Security teams are expected to enhance detection capabilities for chained vulnerabilities, especially those involving public research. Open-source maintainers and enterprises will need to review their CI/CD workflows, especially trust boundaries, and implement stricter controls on fork and commit validation. Ongoing forensic analysis will aim to identify other potential victims and improve understanding of attacker techniques. Additionally, industry efforts are likely to focus on developing faster mitigation deployment processes to counter the rapid weaponization of public research.
Key Questions
How did the attacker exploit the vulnerabilities without stealing npm tokens?
The attacker minted an in-memory OIDC token and exfiltrated credentials via an encrypted messaging network, avoiding the need to steal npm tokens or compromise the publish workflow directly.
What are the three vulnerabilities chained in this attack?
The vulnerabilities are the pull_request_target “Pwn Request” pattern, cache poisoning across trust boundaries in GitHub Actions, and OIDC token extraction from runner memory.
Could similar attacks happen to other open-source projects?
Yes, any project using GitHub Actions workflows and relying on trust boundaries is potentially vulnerable if similar chained vulnerabilities exist or are exploited elsewhere.
What can maintainers do to prevent such attacks?
Implement stricter validation of forks, monitor for suspicious commits, limit trust boundaries, and improve detection of chained vulnerabilities in CI/CD pipelines.
Source: ThorstenMeyerAI.com
