📊 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 in TanStack npm packages to compromise the project. The attack used known weaknesses in GitHub Actions and trust boundaries, highlighting the speed of offensive tradecraft deployment.
On May 11, 2026, a sophisticated supply-chain attack exploited a chain of three publicly documented vulnerabilities in TanStack npm packages, resulting in the publication of 84 malicious package versions within six minutes. The attack was carried out via GitHub Actions, leveraging trust boundaries and known security flaws, and demonstrates how publicly available research can be weaponized faster than defenses can adapt.
The attack involved an attacker creating a malicious fork of TanStack/router on GitHub, then pushing a commit with a fabricated author identity to evade detection. Using the pull_request_target pattern, the attacker triggered workflows that exploited known vulnerabilities in GitHub Actions cache poisoning, OIDC token extraction, and trust boundary crossings. These vulnerabilities—documented in security research from 2024 and 2025—were combined to exfiltrate credentials and publish malicious npm packages without stealing tokens or compromising the publish workflow itself.
Specifically, the attacker created a fork on May 10, 2026, inserted a malicious payload, and then opened a pull request on May 11. The malicious workflows executed, exploiting cache poisoning across fork and base repositories, extracting OIDC tokens from runner memory, and ultimately gaining permission to publish compromised packages to npm. The attack’s success depended on chaining these known vulnerabilities, each necessary but not sufficient alone. The entire operation was completed within hours, illustrating how existing security research can be rapidly turned into offensive tradecraft.
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 the Chain-Driven Supply-Chain Attack
This incident underscores a critical shift: publicly documented security vulnerabilities can be combined and weaponized in real-time, outpacing the deployment of mitigations. It highlights the importance of holistic security practices, especially in open-source ecosystems where trust boundaries are complex. The attack exemplifies the operational risk posed by the rapid dissemination and weaponization of known research, emphasizing the need for faster, integrated defense mechanisms to prevent similar exploits.
Broader Trends in 2026 Supply-Chain Security Breaches
The May 2026 TanStack incident is part of a wider wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign, with other high-profile targets like Mistral AI and UiPath. The attack’s technical foundation is rooted in three well-documented vulnerabilities: the pull_request_target pattern (publicly detailed by GitHub Security Lab in 2021), cache poisoning across trust boundaries (described by Adnan Khan in May 2024), and OIDC token extraction from runner memory (documented by StepSecurity in March 2025). These vulnerabilities, each known for over a year, were exploited in a coordinated manner, illustrating the ‘research-to-tradecraft’ compression problem where offensive capabilities outpace defensive responses.
“The attack demonstrates how publicly available security research can be rapidly weaponized, creating a new paradigm for supply-chain attacks.”
— Thorsten Meyer
Unclear Aspects and Ongoing Investigations
While the technical chain has been reconstructed, details remain limited regarding the attacker’s full operational scope, whether additional vulnerabilities were exploited, and the extent of the compromised packages beyond those publicly identified. The precise timeline of payload deployment and the potential for further exploitation are still under investigation. Additionally, the full impact on affected users and downstream dependencies remains to be assessed.
Next Steps for Defense and Mitigation Strategies
Security teams and open-source maintainers are expected to review and strengthen trust boundary controls, improve detection of malicious forks, and implement faster response protocols for known vulnerabilities. Ongoing research aims to develop automated tools for real-time detection of chained vulnerabilities and malicious activity in CI/CD pipelines. The incident also prompts a reevaluation of security practices around GitHub Actions and package publishing workflows, with industry leaders calling for more integrated security approaches to address the rapid weaponization of public research.
Key Questions
How did the attacker exploit the vulnerabilities without stealing tokens?
The attacker minted an OIDC token in memory and exfiltrated credentials via an encrypted messaging network, Session Protocol, without directly stealing tokens from storage or the publish workflow.
Are all the vulnerabilities used in the attack publicly known?
Yes, each vulnerability exploited is documented in public security research from 2024 and 2025, but their combination and chaining in this context is novel.
What can open-source projects do to prevent similar attacks?
Implement multi-layered security controls, monitor for malicious forks, restrict trust boundaries, and adopt faster incident response protocols to mitigate chained vulnerabilities.
Is the npm publish workflow compromised?
No, the workflow itself was not compromised; the attacker exploited trust boundaries and vulnerabilities to execute malicious actions within the existing process.
Will this incident lead to new security standards?
It is likely to accelerate efforts toward more integrated security standards in CI/CD pipelines and open-source package management, emphasizing rapid detection and response to chained vulnerabilities.
Source: ThorstenMeyerAI.com
