📊 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 compromise TanStack npm packages within six minutes. This incident underscores how known security flaws can be weaponized rapidly, outpacing defenses.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes, using a sophisticated attack that bypassed multiple security controls. This incident underscores the speed at which known security flaws can be weaponized in supply chain attacks, even against well-maintained open-source projects.
The attack was carried out through a sequence of three vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from GitHub Actions runner memory. Each vulnerability was previously documented in security research reports published between March 2025 and May 2024. The attacker created a malicious fork of TanStack/router on May 10, then committed a payload that was later used to trigger the chain. On May 11, the attacker opened a pull request that triggered automated workflows, leading to the publication of 84 malicious package versions across 42 npm packages within six minutes.
Despite the use of two-factor authentication and OIDC trusted publishing, the chain of vulnerabilities allowed the attacker to exfiltrate credentials without stealing npm tokens or compromising the publish workflow directly. The attack leveraged the trust relationships within GitHub Actions and npm publishing processes, exploiting known weaknesses in the CI/CD pipeline architecture.
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.
Network Vulnerability Assessment: Identify security loopholes in your network's infrastructure
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
Accelerate DevOps with GitHub: Enhance software delivery performance with GitHub Issues, Projects, Actions, and Advanced Security
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.npm package security monitoring
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.
Automating DevOps with GitLab CI/CD Pipelines: Build efficient CI/CD pipelines to verify, secure, and deploy your code using real-life examples
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 Publicly Known Vulnerabilities in Supply Chain Attacks
This incident demonstrates that publicly documented security flaws, if not mitigated promptly, can be weaponized by attackers to execute rapid supply chain compromises. It highlights the importance of addressing known vulnerabilities in a timely manner and re-evaluating trust boundaries in CI/CD workflows. The attack also exemplifies how the attack surface expands when multiple vulnerabilities are chained, making even well-secured projects vulnerable if defenders do not adapt quickly.
Broader Trends in 2026 Supply Chain Security Incidents
The May 2026 TanStack attack is part of a broader wave of supply chain compromises, including over 160 packages affected during the ongoing Mini Shai-Hulud campaign. This wave has seen attackers weaponize publicly available research to craft sophisticated, fast-moving attacks that outpace traditional defensive measures. The same day as the TanStack incident, the Google Threat Intelligence Group disclosed a zero-day built with AI, illustrating how AI-augmented offensive capabilities are now operating across multiple dimensions simultaneously. The incident underscores a shift in attacker tradecraft, where publicly available research becomes the foundation for highly effective, rapid exploits.
“The attack demonstrates how the composition of publicly documented vulnerabilities can be weaponized faster than defenders can deploy mitigations, turning known flaws into potent attack chains.”
— Thorsten Meyer
Unresolved Aspects of the Attack Chain and Mitigations
It remains unclear how quickly the TanStack team will implement mitigations for the chain of vulnerabilities and whether additional undisclosed vulnerabilities may have been exploited. The full extent of the attacker’s access and whether other packages or projects were affected are still under investigation. The precise timeline of the attacker’s actions within the compromised environment is also evolving as forensic analysis continues.
Next Steps for Defense and Supply Chain Security
Developers and maintainers are expected to review and patch their CI/CD pipelines, especially focusing on trust boundaries and known vulnerabilities. There will likely be increased scrutiny of open-source supply chains, with recommendations to adopt more rigorous security controls and faster patching cycles. Ongoing forensic analysis aims to assess the full impact of the attack, while security researchers will continue to monitor for similar attack patterns exploiting publicly documented vulnerabilities.
Key Questions
How did attackers exploit publicly documented vulnerabilities so quickly?
The attacker chained three known vulnerabilities—pull request trust issues, cache poisoning, and OIDC token extraction—each previously documented, to rapidly compromise the package publishing process.
Were npm tokens or credentials stolen in this attack?
No, the attacker did not steal npm tokens; instead, they minted an OIDC token in memory and exfiltrated credentials via the Session Protocol, bypassing traditional token theft.
What does this incident mean for open-source security practices?
It underscores the need for faster mitigation of known vulnerabilities, re-evaluation of trust boundaries, and the importance of continuous security monitoring in CI/CD pipelines.
Is this attack part of a larger campaign?
Yes, it is part of the ongoing Mini Shai-Hulud campaign, which has compromised over 160 packages, indicating a broad and sophisticated supply chain attack wave.
Source: ThorstenMeyerAI.com
