📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
An attacker exploited a sequence of three publicly known vulnerabilities to compromise TanStack’s npm packages, demonstrating how public research can be weaponized faster than defenses can adapt. The attack involved chained trust boundary breaches via GitHub Actions workflows.
On May 11, 2026, an attacker exploited a chain of three publicly documented vulnerabilities to compromise TanStack’s npm packages, deploying malicious versions within six minutes. This incident highlights how public security research can be weaponized rapidly, outpacing defensive measures, and underscores systemic risks in software supply chains.
The attack was carried out through a chain 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 was independently documented in security research before the incident, with the attacker combining them to breach trust boundaries within TanStack’s CI/CD pipeline.
Specifically, the attacker created a malicious fork of TanStack/router on May 10, then inserted a crafted commit with a large payload. On May 11, they opened a pull request that triggered automated workflows, which allowed them to forge an OIDC token and exfiltrate credentials without stealing npm tokens or compromising the publish workflow directly. The chain of vulnerabilities enabled the attacker to inject malicious code into published packages, affecting multiple consumers.
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 Public Vulnerabilities in Supply Chain Attacks
This incident demonstrates that publicly known security flaws, when combined, can be exploited at scale faster than organizations can deploy mitigations. It exposes systemic vulnerabilities in open-source CI/CD workflows, emphasizing the need for more robust, layered defenses. The attack also highlights risks associated with reliance on trust boundaries within automated processes, especially when multiple known vulnerabilities are chained together.
Background of the May 2026 Supply Chain Wave
The TanStack compromise is part of a broader wave of supply chain attacks in May 2026, involving over 160 packages across various organizations, including Mistral AI and UiPath. The incident aligns with the disclosure of the first AI-built zero-day by Google Threat Intelligence Group on the same day, illustrating a convergence of offensive capabilities and attack sophistication. The vulnerabilities exploited were all publicly documented between March 2024 and March 2025, underscoring how attacker tradecraft quickly incorporates open research findings.
“The attack demonstrates that the most consequential supply chain incidents in 2026 are not technically novel but are sophisticated compositions of existing public research, executed faster than defenses can adapt.”
— Thorsten Meyer
Unresolved Questions About the Attack Chain and Mitigations
While the forensic analysis has reconstructed the attack chain, details remain unclear regarding the precise extent of compromised systems beyond the npm packages, and how widespread the impact is across the ecosystem. It is also uncertain how quickly organizations can deploy mitigations against such chained vulnerabilities, given their public documentation and known exploits.
Next Steps for Defense and Ecosystem Resilience
Organizations using automated CI/CD workflows should review their trust boundaries and implement stricter controls. Developers and maintainers are advised to monitor for similar attack patterns and incorporate layered security measures. Ongoing forensic investigations aim to determine the full scope of the breach and develop targeted mitigations. Industry-wide, there will likely be increased emphasis on securing trust boundaries and reducing reliance on publicly documented vulnerabilities.
Key Questions
How did the attacker exploit publicly documented vulnerabilities so quickly?
The attacker combined three known vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—each documented in security research before 2026, to chain together an effective attack within minutes of initial access.
What specific vulnerabilities were exploited in the TanStack attack?
The attack relied on the pull_request_target ‘Pwn Request’ pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory, all of which were publicly documented prior to the incident.
Are current mitigations sufficient to prevent similar attacks?
Current mitigations are challenged by the ability to chain multiple vulnerabilities. Organizations need to adopt layered security practices, monitor for suspicious activity, and review trust boundaries to reduce risk.
What lessons can open-source maintainers learn from this incident?
Maintainers should scrutinize their CI/CD workflows for trust boundary violations, implement stricter controls on forks and pull requests, and stay informed about publicly documented vulnerabilities that could be exploited in combination.
Source: ThorstenMeyerAI.com
