📊 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 to compromise TanStack npm packages. The attack was carried out within minutes, demonstrating how public research can be weaponized faster than defenses can respond.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages, using a sophisticated attack that bypassed multiple security layers. This incident highlights how publicly available research can be weaponized rapidly, outpacing defensive measures and demonstrating the evolving threat landscape for software supply chains.
The attack involved the creation of a malicious GitHub fork, insertion of a crafted commit, and exploitation of vulnerabilities in GitHub Actions workflows to exfiltrate credentials. The attacker, identified as user zblgg, created a fork of TanStack/router, inserted malicious code, and used the pull_request_target pattern to inject malicious payloads into the release process. The attack leveraged three previously documented vulnerabilities: the pull_request_target “Pwn Request” pattern (GitHub Security Lab), cache poisoning across trust boundaries (Adnan Khan, 2024), and OIDC token extraction from runner memory (StepSecurity, 2025). These vulnerabilities, each necessary but not sufficient alone, were chained to achieve the compromise. The attack was carried out within a six-minute window, with the malicious versions published across 42 npm packages, though no tokens were stolen directly. The incident was detected 28 hours after the initial fork creation, with forensic analysis confirming the chain of vulnerabilities used.
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.
Incident Response Analyst Call Humor Soc Cybersecurity T-Shirt
For the infosec professional who lives by zero trust, ethical hacking and incident response at 3am. Always On…
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 Chained Vulnerabilities in Supply Chain Attacks
This incident underscores how publicly available security research can be rapidly weaponized, enabling highly sophisticated supply-chain attacks. It demonstrates that the most impactful 2026 incidents are less about novel attack techniques and more about the composition of known vulnerabilities executed at high speed. For open-source maintainers and enterprise users, this highlights the urgent need for faster deployment of mitigations and more robust security review processes to keep pace with attacker tradecraft.
Broader Trends in 2026 Supply-Chain Security Breaches
The May 2026 TanStack attack is part of a wider wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. The attack coincided with the disclosure of the first AI-built zero-day by Google Threat Intelligence Group, illustrating a convergence of AI-augmented offensive capabilities. Past research from GitHub Security Lab, Adnan Khan, and StepSecurity had already documented each vulnerability exploited in the attack, but the chain’s assembly into a single operation demonstrates how attacker tradecraft has compressed into rapid, high-impact sequences. TanStack’s security measures, including 2FA and OIDC trusted publishing, were insufficient to prevent this chain, emphasizing the need for systemic security improvements across open-source ecosystems.
“The TanStack incident exemplifies how publicly available security research becomes attacker tradecraft, executed faster than defenders can adapt.”
— Thorsten Meyer, researcher
Unresolved Aspects of the Chain Exploitation
While the chain of vulnerabilities has been reconstructed in forensic detail, it remains unclear how widespread the exploitation tactics are beyond the TanStack incident. It is also uncertain whether other packages or projects have been similarly targeted using the same chain, or if additional undisclosed vulnerabilities are being exploited in parallel. The full extent of attacker infrastructure and future campaigns remains under investigation.
Next Steps for Detection and Prevention
Security researchers and open-source maintainers are expected to analyze this attack chain further, with recommendations to improve detection of malicious forks, commits, and workflow manipulations. Organizations are advised to review their CI/CD pipelines, especially trust boundaries, and deploy faster mitigation strategies. Ongoing forensic investigations aim to determine if other packages have been compromised using similar methods, and whether new vulnerabilities are being weaponized in real-time.
Key Questions
How did the attacker bypass security measures in TanStack?
The attacker exploited a chain of publicly documented vulnerabilities—specifically, the pull_request_target pattern, cache poisoning, and OIDC token extraction—each of which was known but not mitigated quickly enough.
Were any tokens or credentials stolen during the attack?
No tokens were stolen; the attacker minted an OIDC token in memory and exfiltrated credentials via an encrypted messaging network without using attacker-controlled C2 infrastructure.
Could this type of attack happen to other open-source projects?
Yes, any project relying on CI/CD workflows and trust boundaries is vulnerable if known vulnerabilities are not promptly mitigated. The attack chain is applicable broadly across similar ecosystems.
What can maintainers do to prevent similar incidents?
Implement rapid mitigation for known vulnerabilities, scrutinize trust boundaries, monitor for suspicious fork activity, and consider stricter controls on CI/CD processes.
Source: ThorstenMeyerAI.com
