📊 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 known vulnerabilities to compromise TanStack npm packages. The attack leveraged research-published flaws, highlighting the speed of offensive tradecraft outpacing defenses.
On May 11, 2026, attackers successfully compromised the TanStack npm packages by exploiting a chain of three publicly documented vulnerabilities, all of which had been known in security research for months. This attack was executed within six minutes, demonstrating how publicly available research can be weaponized faster than defenses can respond. The incident underscores the increasing sophistication and speed of supply-chain attacks driven by publicly available tradecraft.
The attack involved publishing 84 malicious versions across 42 TanStack npm packages, using a trusted GitHub Actions workflow with OIDC authentication. The attacker created a fork of the TanStack/router repository, inserted malicious code via a crafted commit, and then used a pull request targeting the main branch. By leveraging a chain of three known vulnerabilities—pull_request_target abuse, cache poisoning across trust boundaries, and OIDC token extraction—the attacker gained write access to the npm registry without stealing tokens or compromising the publish workflow directly.
Each vulnerability had been previously documented: the pull_request_target pattern by GitHub Security Lab, cache poisoning by Adnan Khan in May 2024, and OIDC token extraction by StepSecurity in March 2025. None alone was sufficient; the chain’s effectiveness depended on their combination, which bridged multiple trust boundaries within the CI/CD pipeline. The attack was executed within hours of the initial fork creation, with the malicious code deployed via GitHub workflows that trusted the attacker’s fork.
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 for Supply-Chain Security in Open Source
This incident illustrates how publicly available security research can be weaponized in real-world attacks, especially when multiple vulnerabilities are chained together. It highlights the speed at which adversaries can adapt and execute sophisticated supply-chain attacks, often outpacing the deployment of mitigations. For open-source maintainers and enterprise users, this underscores the importance of re-evaluating trust boundaries, implementing stricter code review processes, and monitoring for chained vulnerabilities in their CI/CD pipelines.
Pre-Existing Research and the 2026 Supply-Chain Wave
The May 2026 attack on TanStack is part of a broader wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. Prior to this incident, researchers published findings on the vulnerabilities exploited: GitHub’s pull_request_target abuse (by GitHub Security Lab, 2021), cache poisoning across trust boundaries (by Adnan Khan, 2024), and OIDC token extraction (by StepSecurity, 2025). These publications provided attacker tradecraft that was quickly weaponized in the TanStack attack, demonstrating a direct link between research and operational threat.
The incident also coincided with the disclosure of a zero-day by Google Threat Intelligence Group, illustrating a convergence of offensive capabilities driven by AI-augmented research, with both events occurring on the same day. This confluence signals a shift where publicly documented vulnerabilities are no longer just academic but are actively exploited in sophisticated campaigns.
“The TanStack incident exemplifies how well-documented vulnerabilities can be combined in real-time to execute complex supply-chain attacks, often faster than defenders can respond.”
— Thorsten Meyer
Unresolved Aspects of the Attack Chain and Defense Gaps
While the technical chain has been reconstructed with high confidence, it remains unclear how widespread the exploitation of similar chains might be across other projects. The full extent of the attack’s impact on downstream systems and whether additional malicious payloads were deployed is still under investigation. Furthermore, the exact timeline of detection and response by the TanStack team is being evaluated, and it is not yet clear how quickly mitigations can be deployed at scale to prevent similar attacks.
Future Steps for Mitigating Chained Supply-Chain Attacks
Security teams and open-source maintainers are expected to enhance their review processes, implement stricter trust boundary controls, and monitor for chained vulnerabilities. The incident has prompted calls for better detection tools that can identify complex attack chains in CI/CD pipelines. Ongoing investigations will determine if additional malicious activity occurred and how defenses can be improved to prevent similar exploits, especially those leveraging publicly available research.
Key Questions
How did the attacker manage to exploit these vulnerabilities so quickly?
The attacker combined three known vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—each documented in public research, to rapidly chain their effects within hours of the initial fork creation.
Are other open-source projects at similar risk?
Yes, any project using similar CI/CD workflows and trust boundaries could be vulnerable if these chained vulnerabilities are present and unmitigated. The attack demonstrates the importance of reviewing trust assumptions and applying mitigations proactively.
What can maintainers do to prevent similar attacks?
Implement stricter code review policies, monitor for suspicious activity in forks and pull requests, and consider isolating trust boundaries within CI/CD pipelines. Regularly reviewing published research for potential attack vectors is also recommended.
Is this incident an example of a zero-day attack?
No, the attack exploited publicly documented vulnerabilities, but combined in a novel way. It highlights how existing research can be weaponized rapidly, blurring the line between known flaws and zero-day exploits.
Source: ThorstenMeyerAI.com
