📊 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 was enabled by combining previously documented flaws, demonstrating how public research can be weaponized faster than defenses adapt.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack’s npm packages, using a sophisticated combination of known security flaws to bypass defenses. This incident underscores how publicly available research can be weaponized rapidly, with significant implications for supply-chain security.
The attack involved publishing 84 malicious versions across 42 TanStack packages within six minutes, using an OIDC trusted-publisher binding via GitHub Actions. The attacker created a fork of TanStack/router, injected malicious code via a crafted commit, and exploited three known vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across fork-base trust boundary, and OIDC token extraction from GitHub Actions runner memory. Each vulnerability was publicly documented before the attack, with the last being disclosed in March 2025 by StepSecurity.
Analysis shows that no single vulnerability was sufficient; the attack relied on chaining these flaws, each bridging trust boundaries in the CI/CD pipeline. The attacker minted an in-memory OIDC token and exfiltrated credentials through an encrypted messaging network, with no attacker-controlled command-and-control infrastructure. The incident was detected within 28 hours, after which TanStack responded with mitigations. The attack exemplifies how public research can be weaponized swiftly, outpacing defensive deployment.
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
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.
Securing the CI/CD Pipeline: Best Practices for DevSecOps
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.
The Android Malware Handbook: Detection and Analysis by Human and Machine
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 Public Research-Driven Supply-Chain Attacks
This incident highlights a critical shift in supply-chain security: vulnerabilities documented in public research are increasingly exploited in sophisticated attacks, often faster than defenders can deploy mitigations. The chaining of three known flaws demonstrates that no single vulnerability is sufficient; instead, attackers combine multiple known issues to breach defenses. For open-source maintainers and enterprise users, this underscores the importance of holistic security reviews and rapid response capabilities to counter the weaponization of public research.
Broader Trends in 2026 Supply-Chain Security Breaches
The TanStack incident is part of a wider wave of supply-chain compromises in May 2026, affecting over 160 packages in the npm ecosystem, including Mistral AI, UiPath, and Squawk. This wave, dubbed the Mini Shai-Hulud campaign, reflects a pattern where attackers leverage publicly documented vulnerabilities to execute high-impact breaches. Notably, the same day as the TanStack attack, the Google Threat Intelligence Group disclosed an AI-built zero-day, illustrating a convergence of offensive techniques in the same timeframe.
Prior research, spanning from 2024 to 2025, had documented each vulnerability involved in this chain, emphasizing the gap between knowledge and deployment of mitigations. The incident exemplifies the ‘research-to-tradecraft’ compression problem, where publicly available security findings are rapidly weaponized, often outpacing defense responses.
“The TanStack attack demonstrates how publicly documented vulnerabilities, when chained, can be exploited faster than defenses can respond, marking a turning point in supply-chain security.”
— Thorsten Meyer
Unresolved Questions About the Attack Chain and Mitigations
While the technical chain has been reconstructed from forensic analysis, it remains unclear how widespread the exploitation of this chain is beyond TanStack, and whether additional variants or similar attack patterns are emerging. The speed at which defenses can be deployed to counter such chained vulnerabilities is also uncertain, given the rapid weaponization observed.
Next Steps for Defenders and Open-Source Maintainers
Organizations should review their CI/CD pipelines for similar vulnerabilities, especially the public research documented attack vectors. Developers and maintainers are encouraged to adopt rapid patching practices and enhance monitoring for suspicious activities. Ongoing research into automated detection of chained vulnerabilities will be critical to prevent similar incidents. Additionally, the security community is likely to scrutinize the chain for further variants and develop targeted mitigations.
Key Questions
How did attackers exploit publicly documented vulnerabilities so quickly?
Attackers combined three known vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—each documented in public research, to craft a chain that bypassed defenses. They automated the process to exploit the vulnerabilities within minutes.
What specific vulnerabilities were chained in this attack?
The attack involved the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from GitHub runner memory, all documented prior to the incident.
Are these vulnerabilities still exploitable today?
Mitigations are available, but the attack demonstrates that chaining publicly known vulnerabilities can still be effective if defenses are not rapidly deployed. Organizations should review their pipelines for these issues.
What does this incident mean for open-source security?
It underscores the need for holistic security practices, rapid patching, and awareness of how publicly available research can be weaponized. Maintaining vigilance against complex attack chains is essential.
Will new mitigations or standards be developed in response?
Likely, the security community will prioritize developing automated detection tools and best practices to address chained vulnerabilities, especially as such incidents become more common.
Source: ThorstenMeyerAI.com
