📊 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. This incident highlights how attacker tradecraft rapidly evolves by combining existing research, outpacing defenders.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to publish malicious versions of TanStack npm packages within six minutes, bypassing security controls and exfiltrating credentials through trusted GitHub workflows. This incident underscores how publicly available research can be weaponized rapidly against the software supply chain, even by security-conscious maintainers.
The attack involved the publication of 84 malicious package versions across 42 TanStack packages, authenticated via GitHub Actions OIDC trusted-publisher binding. The attacker created a fork of TanStack/router, inserted malicious code, and used a chain of three known vulnerabilities to cross trust boundaries within the CI/CD pipeline. Notably, no npm tokens were stolen, and the npm publish workflow remained intact, but the attacker minted an in-memory OIDC token and exfiltrated credentials via the encrypted Session Protocol network.
The vulnerabilities exploited were: the pull_request_target “Pwn Request” pattern, cache poisoning across fork-base trust boundaries, and extraction of OIDC tokens from GitHub Actions runner memory. Each was publicly documented before the attack, with the latest research published 12 months prior. The attack demonstrates how these vulnerabilities, each necessary but insufficient alone, can be combined to produce a sophisticated supply chain compromise. The incident coincides with the same day as the Google Threat Intelligence Group’s disclosure of an AI-built zero-day, illustrating a broader trend of rapid, research-based offensive operations.
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.
Software Supply Chain Defense: Securing Build Environments, Toolchains, and CI/CD Infrastructure Against Advanced Threats
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
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.
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 vulnerability scanner
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 of the Chain-Driven Supply Chain Attack
This incident exemplifies how publicly available security research can be rapidly weaponized, creating a supply chain attack that outpaces traditional defense deployment. It highlights the operational risk for open-source maintainers and enterprise users relying on npm packages, emphasizing the need for improved detection and mitigation strategies. The attack also demonstrates that the most consequential incidents in 2026 are less about novel exploits and more about the composition of existing research into sophisticated tradecraft, facilitated by AI and automation.
Public Research and the Evolution of Attack Tradecraft
Over the past year, multiple publicly documented vulnerabilities have been exploited in high-profile supply chain incidents. The TanStack attack builds upon prior research: the pull_request_target pattern (GitHub Security Lab, 2021), cache poisoning across trust boundaries (Adnan Khan, May 2024), and OIDC token extraction from runner memory (StepSecurity, March 2025). Each of these findings was known in the security community, yet their combination in a single attack reflects a shift towards research-to-tradecraft compression, where attacker capabilities evolve faster than defenders can deploy mitigations. The incident is part of the ongoing Mini Shai-Hulud campaign, which has compromised over 160 packages, including Mistral AI and UiPath, illustrating the scale and sophistication of the current supply chain threat landscape.
“The TanStack incident exemplifies how publicly available research can be rapidly weaponized, creating a new paradigm for supply chain attacks.”
— Thorsten Meyer, security researcher
Remaining Questions About the Attack Chain and Impact
While the forensic analysis confirms the chain of vulnerabilities exploited, it remains unclear how widespread the initial compromise was beyond the TanStack packages, and whether other projects have been similarly targeted using this method. Details about the attacker’s full operational infrastructure and whether additional payloads are in circulation are still emerging. Moreover, the precise timeline of detection and response efforts by TanStack and other affected maintainers is under investigation.
Future Steps for Detection and Prevention of Similar Attacks
Security teams and open-source maintainers are expected to review and strengthen CI/CD trust boundaries, especially around pull request workflows and artifact caching. Enhanced monitoring for suspicious fork activity and malicious commits will become a priority. Industry-wide, there will be a push to develop automated detection tools that can identify the chaining of known vulnerabilities in real-time, reducing the window for attacker exploitation. Further research into resilient trust models for software supply chains is anticipated, alongside increased collaboration between security researchers and platform providers.
Key Questions
How did the attacker bypass security controls in the TanStack attack?
The attacker exploited a chain of publicly documented vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—to cross trust boundaries within the CI/CD pipeline, allowing malicious package publication without stealing npm tokens.
Are other npm packages or projects at similar risk?
Yes, the attack demonstrates how known vulnerabilities can be combined to target similar trust boundary weaknesses in other projects, especially those using GitHub Actions workflows with trusted publishing and cache sharing.
What can maintainers do to prevent such attacks?
Implement stricter controls on pull request workflows, monitor fork activity, avoid sharing cache across trust boundaries, and adopt automated detection tools for known vulnerability chains.
Is this attack technique new?
No, the attack used publicly documented vulnerabilities; the novelty lies in their combination and rapid execution, facilitated by AI-augmented tradecraft and automation.
Source: ThorstenMeyerAI.com
