📊 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 used public research to bypass defenses, highlighting the speed at which attacker tradecraft now evolves faster than mitigation deployment.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages, using public research to execute a sophisticated supply-chain attack faster than defenders could deploy mitigations. The incident involved the publication of malicious package versions via GitHub Actions workflows, without theft of npm tokens or workflow compromise, revealing a new level of attacker agility.
The attack was carried out by a malicious actor who created a fork of the TanStack/router repository on GitHub, then added a malicious commit using a forged author identity. The attacker used a combination of three known vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across trust boundaries, and extraction of OIDC tokens from GitHub Actions runners. These vulnerabilities, each documented in public security research before 2026, were chained together to breach trust boundaries and publish malicious npm package versions within minutes.
Specifically, the attacker created a fork on May 10, then injected malicious code via a commit. On May 11, they opened a pull request that triggered GitHub Actions workflows, which executed malicious payloads. The attacker minted an OIDC token in memory and exfiltrated credentials through Session Protocol, a secure messaging network, without stealing npm tokens or compromising the workflow itself. The attack exploited the fact that each vulnerability, while documented publicly, could be combined to bypass defenses—highlighting the attack surface’s complexity.
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
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.
Python Cybersecurity Automation Tips – Efficient security monitoring and penetration testing automation using scripts and tools – (Japanese Edition)
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 products
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.
Impact of Public Research-Driven Supply-Chain Attacks
This incident underscores how publicly available security research can be weaponized rapidly, outpacing typical defense deployment timelines. The attack demonstrates that the most consequential supply-chain compromises in 2026 are less about novel exploits and more about combining existing vulnerabilities documented in the public domain. It highlights the need for faster, more integrated mitigation strategies and better understanding of trust boundaries in CI/CD workflows.
Public Research and the Evolution of Attack Tradecraft
Since 2024, security researchers have documented vulnerabilities in GitHub Actions workflows, trust boundaries, and token extraction mechanisms. The three vulnerabilities involved are the pull_request_target pattern (documented by GitHub Security Lab), cache poisoning across trust boundaries (by Adnan Khan), and OIDC token extraction from runner memory (by StepSecurity). Each was known publicly for 12 months or more before the attack, illustrating the gap between research publication and effective defense deployment. The May 11 incident is part of the broader Mini Shai-Hulud campaign, which compromised over 160 packages across multiple vendors, exploiting the same chain of vulnerabilities.
“The TanStack incident exemplifies how publicly documented vulnerabilities can be combined into a potent attack chain, executed faster than defenses can respond.”
— Thorsten Meyer
Uncertainties About the Attack Chain and Future Risks
While the chain of vulnerabilities has been reconstructed from forensic analysis, some details about the attacker’s full operational scope and whether additional undisclosed vulnerabilities were exploited remain unclear. The extent of the breach impact beyond package publication is still being assessed, and the speed at which defenders can deploy mitigations against such chained attacks is uncertain.
Operational Responses and Mitigation Strategies Moving Forward
Security teams are expected to prioritize patching trust boundary vulnerabilities, improve CI/CD workflow security, and develop faster detection mechanisms. GitHub and npm are likely to release updated security controls, and open-source maintainers are advised to review their workflows for similar chains. Ongoing analysis will determine if additional vulnerabilities are being exploited in other campaigns, and the broader supply-chain ecosystem will need to adapt to the rapid evolution of attacker tradecraft.
Key Questions
How did the attacker bypass security measures in the TanStack attack?
The attacker exploited a chain of publicly documented vulnerabilities—specifically, the pull_request_target pattern, cache poisoning, and OIDC token extraction—each of which alone was insufficient, but together enabled the breach.
Are other npm packages or open-source projects at similar risk?
Yes, the attack demonstrates that any project using CI/CD workflows with trust boundaries is potentially vulnerable if these specific vulnerabilities are present or can be exploited in combination.
What can maintainers do to prevent similar attacks?
Maintainers should review their trust boundaries, restrict access in workflows, monitor for suspicious commits, and implement faster detection of chained vulnerabilities, especially those documented publicly in the past.
Will new mitigations be effective against future chained attacks?
While mitigations can reduce risk, the incident shows that attacker tradecraft evolves rapidly by combining known vulnerabilities. Continuous security review and faster deployment of defenses are essential.
Source: ThorstenMeyerAI.com
