📊 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 within six minutes. The attack highlights the speed at which public research can be weaponized and the need for faster defense deployment.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to publish 84 malicious versions of TanStack npm packages within six minutes, without stealing tokens or compromising the publish workflow itself. This incident underscores how publicly available security research can be rapidly weaponized, outpacing defenders’ mitigation efforts.
The attack involved chaining three vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory. Each was previously documented in public security research, but their combination enabled the breach. The attacker created a fork of TanStack/router on May 10, then inserted malicious code through a crafted commit on May 10 at 23:29. The malicious pull request was opened on May 11 at 10:49, triggering workflows that allowed the attacker to mint an OIDC token in memory and exfiltrate credentials via an encrypted messaging network, without stealing tokens or compromising the package registry directly.
The attack was executed using operational tradecraft based on publicly available research findings from GitHub Security Lab, Adnan Khan, and StepSecurity, all published in 2024 and 2025. The chain of vulnerabilities bridges trust boundaries within the CI/CD pipeline, enabling malicious code to reach the npm registry. The incident affected over 160 packages in the ongoing Mini Shai-Hulud campaign, which includes other high-profile compromises like Mistral AI and UiPath.
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 Chain Exploitation for Supply Chain Security
This incident demonstrates that the most impactful supply chain attacks in 2026 are no longer reliant on novel vulnerabilities but on the rapid combination of publicly known flaws. It highlights the challenge for defenders to deploy mitigations faster than attackers can weaponize published research. The breach underscores the need for improved security practices, faster patching, and better detection of chained vulnerabilities in open-source ecosystems, especially given the high competence of the attacker and the pre-existing public research.
Broader Trends in Public Research and Supply Chain Attacks
The May 2026 TanStack attack is part of a wider wave of supply chain compromises driven by publicly available security research. Over the past year, researchers have documented vulnerabilities in GitHub Actions workflows, cache trust boundaries, and token extraction methods—each of which has been exploited in real-world attacks. The incident underscores a persistent gap between research publication and defensive deployment, with attackers weaponizing these findings at a pace that outstrips mitigation efforts. This event coincides with the first AI-built zero-day disclosed by Google Threat Intelligence Group, illustrating the convergence of AI-augmented offensive techniques and existing vulnerabilities.
“The TanStack incident exemplifies how publicly documented vulnerabilities can be chained to produce highly effective, rapid supply chain attacks, revealing a fundamental challenge in defense speed.”
— Thorsten Meyer, security researcher
Remaining Questions About Attack Scope and Mitigations
It is still unclear how widespread the malicious versions have become beyond the initial breach, and whether additional undetected exploitation has occurred. The precise detection and mitigation measures that will effectively prevent similar chained attacks remain under development. Details about whether the attacker maintained persistence or targeted specific repositories are also not yet confirmed.
Next Steps for Defense and Monitoring in Open-Source Ecosystems
Security teams are expected to enhance detection of chained vulnerabilities, implement faster patching workflows, and improve monitoring of CI/CD pipelines. The incident underscores the urgency for community-wide adoption of best practices, such as stricter code review of forks, better control of trust boundaries, and real-time vulnerability scanning. Ongoing forensic analysis aims to determine the full extent of the breach and refine mitigation strategies to prevent future incidents.
Key Questions
How did the attacker chain the vulnerabilities in the TanStack attack?
The attacker exploited three publicly documented vulnerabilities: the pull_request_target pattern, cache poisoning across trust boundaries, and OIDC token extraction from runner memory. Combining these allowed malicious code to reach the npm registry without stealing tokens or directly compromising the publish workflow.
What does this attack reveal about the security of open-source supply chains?
It shows that publicly available research can be weaponized rapidly, making supply chain security dependent not only on technical controls but also on the speed of defense deployment and community awareness.
Are existing mitigations sufficient to prevent future chained attacks?
Current mitigations are insufficient against such complex, chained exploits. The incident calls for faster patching, improved detection, and stricter trust boundaries within CI/CD pipelines.
Will this lead to changes in how open-source projects handle security?
Yes, it is likely to accelerate adoption of stricter review processes, automated vulnerability scanning, and better control of external dependencies and forks.
What role does public research play in offensive cybersecurity?
Public research provides valuable insights that can be weaponized by attackers, highlighting a need for balancing transparency with the potential for misuse and for faster deployment of defenses.
Source: ThorstenMeyerAI.com
