📊 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 three publicly documented vulnerabilities to compromise TanStack’s npm packages. The attack was rapid and involved chaining known flaws, highlighting systemic security issues in open-source supply chains.
On May 11, 2026, attackers successfully compromised TanStack npm packages by exploiting a chain of three publicly known vulnerabilities, demonstrating the rapid weaponization of security research in the open-source ecosystem. The attack, executed via GitHub Actions and OAuth trust relationships, did not involve token theft but exfiltrated credentials through in-memory OIDC tokens. This incident underscores systemic security gaps that enable complex supply-chain attacks.
The attack began on May 10 when the attacker created a fork of TanStack/router, deliberately renamed to evade detection. They then committed malicious code containing a payload designed to exploit known vulnerabilities in the CI/CD pipeline. On May 11, the attacker opened a pull request using the pull_request_target pattern, which triggered automated workflows configured with trusted access. These workflows, vulnerable to cache poisoning and OIDC token extraction, allowed the attacker to mint an in-memory token and exfiltrate credentials via an encrypted messaging network. 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 vulnerability alone was insufficient; together, they enabled the compromise.
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.
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 for Supply-Chain Security in 2026
This incident exemplifies how publicly documented vulnerabilities can be combined into sophisticated attack chains, leading to rapid and large-scale compromises in open-source ecosystems. It reveals that the most impactful supply-chain incidents are no longer about novel exploits but about the composition and rapid deployment of existing research. The attack highlights systemic weaknesses in trust boundaries within CI/CD pipelines and emphasizes the need for more robust defenses against chained vulnerabilities.
Broader Trends in 2026 Supply-Chain Attacks
The TanStack incident is part of a broader wave of supply-chain compromises in May 2026, affecting over 160 packages across multiple organizations, including Mistral AI and UiPath. These attacks leverage publicly available research, weaponized faster than defenders can deploy mitigations. The same day as the TanStack breach, Google Threat Intelligence disclosed an AI-generated zero-day, illustrating the convergence of AI-augmented offensive capabilities and systemic vulnerabilities. The incident underscores a shift where attacker tradecraft is increasingly based on recombining existing research into effective attack chains, rather than relying on novel exploits.
“The attack demonstrates how published security research becomes attacker tradecraft, executed faster than defenses can adapt.”
— Thorsten Meyer
Remaining Questions About the Attack Chain
Details about the specific extent of the breach, such as whether malicious code was successfully deployed in production or if further exfiltration occurred, remain unclear. The full scope of compromised systems and the potential for ongoing exploitation are still being assessed. Additionally, the precise operational tradecraft used by the attacker beyond publicly documented vulnerabilities has not been fully disclosed.
Operational and Defensive Responses Moving Forward
Organizations using similar CI/CD pipelines are expected to review and strengthen their trust boundaries, especially around pull request workflows and token management. Increased monitoring for chained vulnerabilities and rapid deployment of mitigations are anticipated. The incident is likely to accelerate industry discussions on supply-chain security, with a focus on automating detection and response to chained vulnerabilities, and revising trust models within CI/CD systems.
Key Questions
How did the attacker exploit the vulnerabilities without stealing tokens?
The attacker minted an in-memory OIDC token during the workflow execution and exfiltrated credentials via an encrypted messaging network, avoiding the need to steal stored tokens.
Are similar vulnerabilities present in other open-source projects?
Yes, all three vulnerabilities exploited are publicly documented and affect multiple projects. The attack demonstrates the risk of chaining known flaws in supply-chain attacks.
What can open-source maintainers do to prevent similar attacks?
Implement stricter trust boundary controls, limit the use of pull_request_target workflows, and enhance monitoring for chained vulnerabilities. Regularly reviewing and updating security practices is also crucial.
Is there an immediate risk to users of TanStack packages?
As of now, no malicious code has been confirmed in production, but the breach underscores the need for vigilance and rapid response to potential supply-chain compromises.
Source: ThorstenMeyerAI.com
