📊 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, leading to a supply chain compromise. The attack was executed within minutes, highlighting the rapid evolution of AI-augmented offensive techniques.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack’s npm packages, demonstrating how AI-augmented offensive tradecraft can operate faster than defenders can deploy mitigations. The attack involved malicious package versions published within six minutes, without theft of npm tokens, by leveraging trusted GitHub Actions workflows. This incident underscores the growing sophistication of supply chain attacks in 2026.
The attack was initiated on May 10, when the attacker, using the GitHub user zblgg, created a fork of TanStack/router and inserted malicious commits. The attacker used forged identities and operational tradecraft to evade detection. On May 11, a pull request was opened against the main repository, triggering GitHub Actions workflows that, due to chained vulnerabilities, allowed the attacker to exfiltrate credentials and publish malicious package versions in a six-minute window. The vulnerabilities exploited include the pull_request_target pattern, GitHub Actions cache poisoning, and OIDC token extraction from runner memory. All three vulnerabilities had been publicly documented prior to the attack, but their combination enabled the breach.
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.![Norton 360 Deluxe, Antivirus software for 3 Devices with Auto-Renewal – Includes Advanced AI Scam Protection, VPN, Dark Web Monitoring & PC Cloud Backup [Download]](https://m.media-amazon.com/images/I/51lgakZZwpL._SL500_.jpg)
Norton 360 Deluxe, Antivirus software for 3 Devices with Auto-Renewal – Includes Advanced AI Scam Protection, VPN, Dark Web Monitoring & PC Cloud Backup [Download]
ONGOING PROTECTION Download instantly & install protection for 3 PCs, Macs, iOS or Android devices in minutes!
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 demonstrates that the most impactful supply chain breaches in 2026 are no longer driven by novel exploits but by the rapid composition of known vulnerabilities. The attack highlights how AI-augmented attack tradecraft can combine multiple publicly known flaws to breach even well-defended open-source projects. It exposes the accelerating pace at which adversaries can operationalize research into effective attack chains, outpacing defenders’ mitigation efforts. The incident underscores the urgent need for improved detection, faster response, and more resilient security practices in open-source ecosystems and enterprise supply chains.
Public Research and the Evolution of Attack Techniques
The attack leverages three vulnerabilities that were individually documented in public security research: the pull_request_target ‘Pwn Request’ pattern (GitHub Security Lab, 2019), cache poisoning across trust boundaries (Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runners (StepSecurity, March 2025). Each of these vulnerabilities was known, with detailed mitigation strategies available for years. Yet, the attack demonstrates how attackers can chain these known flaws into a single, effective exploit, exploiting the ecosystem’s slow pace in deploying mitigations. The incident is part of a broader wave of supply chain compromises in May 2026 affecting over 160 packages, including high-profile entities like Mistral AI and UiPath.
“The TanStack incident exemplifies how publicly documented vulnerabilities can be combined into a potent attack chain, executed faster than defenders can respond.”
— Thorsten Meyer
Unconfirmed Aspects and Ongoing Investigations
While the technical chain has been reconstructed based on forensic analysis, some details about the attacker’s full scope of access and potential additional payloads remain unconfirmed. It is also unclear whether other packages or projects have been similarly compromised using this chain or variations thereof. The full extent of the breach and the attacker’s objectives are still under investigation by security teams.
Future Steps and Defensive Measures Post-Incident
Security teams are working to deploy targeted mitigations against the chained vulnerabilities, including stricter review of pull requests involving trusted workflows, improved detection of suspicious fork activity, and enhanced runtime security for GitHub Actions. The incident is prompting the ecosystem to reevaluate supply chain security practices, with calls for faster patching, better monitoring, and more resilient architectural designs. Additional forensic analysis and community sharing of attack details are expected in the coming weeks to prevent similar breaches.
Key Questions
How did the attacker exploit the vulnerabilities without stealing npm tokens?
The attacker minted an OIDC token in memory during the GitHub Actions runtime and exfiltrated credentials via the encrypted Session Protocol, avoiding the need to steal tokens directly.
Are all affected packages now secure?
Security teams are actively deploying mitigations, but given the chain of vulnerabilities, complete security depends on patching and architectural adjustments. It is recommended to monitor for suspicious activity and update dependencies promptly.
Could this type of attack happen again with other projects?
Yes, any project relying on trusted workflows and public vulnerabilities could be vulnerable if similar chaining techniques are employed. Organizations should review their CI/CD security practices accordingly.
What lessons can open-source maintainers learn from this incident?
Maintainers should implement stricter review processes for pull requests, especially those involving trusted workflows, and monitor for unusual fork or commit activity. Rapid patching and layered security controls are essential.
Source: ThorstenMeyerAI.com
