📊 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 known vulnerabilities to compromise TanStack npm packages within six minutes. The attack used public research and trust boundary breaches, highlighting the speed of modern supply-chain threats.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to publish 84 malicious versions of TanStack npm packages within six minutes, bypassing security defenses through a combination of trust boundary breaches.
The attack was carried out by a malicious actor who created a fork of the TanStack/router repository, inserted a malicious commit, and used GitHub Actions workflows to exfiltrate credentials without stealing tokens or compromising the publish workflow directly. The chain involved exploiting known vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across fork-base trust boundaries, and OIDC token extraction from GitHub Actions runtime. Each vulnerability was previously documented in security research published between March 2025 and May 2024, but their combination enabled the attack.
The attacker used forged identities and operational tradecraft, such as renaming forks to evade detection and fabricating commit author identities. The malicious commit added a large JavaScript payload, which was later invoked via a pull request that triggered the malicious package publishing. The breach was detected 28 hours after initial fork creation, illustrating the rapidity of the attack chain.
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.
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.code repository security audit
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 underscores how publicly available security research can be weaponized when combined into attack chains, outpacing defenders’ ability to deploy mitigations. It demonstrates that the most consequential supply-chain attacks in 2026 are less about novel exploits and more about sophisticated compositions of existing vulnerabilities, executed faster than security teams can respond.
For open-source maintainers and enterprise users, this highlights the importance of understanding trust boundaries, monitoring for operational tradecraft, and deploying layered defenses against chained vulnerabilities.
Broader Trends in 2026 Supply-Chain Attacks
The May 2026 TanStack incident is part of a wider wave of supply-chain compromises affecting over 160 packages, including Mistral AI, UiPath, and Squawk, within the ongoing Mini Shai-Hulud campaign. The attack leverages publicly documented vulnerabilities that have been known for over a year, illustrating a shift where attacker tradecraft is increasingly based on combining existing research rather than developing new exploits. The same day as the TanStack breach, Google Threat Intelligence disclosed a zero-day built with AI, further emphasizing the rapid pace of offensive innovation in this space.
Previous research by GitHub Security Lab, Adnan Khan, and StepSecurity detailed vulnerabilities such as cache poisoning, OIDC token extraction, and unsafe pull request handling, all of which were exploited in this chain. The attack exemplifies the challenge of defending against fast-moving, research-driven supply-chain threats.
“The TanStack incident demonstrates how publicly available security research can be weaponized in a matter of hours, outpacing traditional defense mechanisms.”
— Thorsten Meyer, security researcher
What Details Are Still Unclear About the Attack Chain
While the technical chain of vulnerabilities has been reconstructed from forensic analysis, some aspects remain uncertain, such as the full extent of the attacker’s operational tradecraft and whether additional vulnerabilities or exploits were involved beyond those publicly documented. The precise scope of compromised systems and potential further exfiltration are still under investigation. Additionally, the effectiveness of current mitigations against similar future attacks has yet to be fully assessed.
Next Steps for Defense and Monitoring
Security teams are expected to review and strengthen trust boundary controls, monitor for signs of chained vulnerabilities, and incorporate lessons from this incident into broader supply-chain security strategies. Ongoing analysis will determine if additional vulnerabilities were exploited or if similar attack patterns are emerging elsewhere. Industry-wide, there will likely be increased scrutiny of open-source package security, with a focus on layered defenses against known, publicly documented vulnerabilities.
Key Questions
How did the attacker chain these vulnerabilities so quickly?
The attacker combined publicly documented vulnerabilities—trust boundary breaches, cache poisoning, and token exfiltration—using operational tradecraft to automate and accelerate the attack, executing within six minutes of initial fork creation.
Were any tokens or credentials stolen during the attack?
No npm tokens were stolen. The attacker minted an OIDC token in memory and exfiltrated credentials via the Session Protocol, a secure messaging network, without direct C2 infrastructure or token theft.
What can open-source maintainers do to prevent similar attacks?
Maintainers should enhance trust boundary controls, monitor for suspicious activity, and implement layered security measures. Understanding how vulnerabilities can combine is key to developing effective defenses against fast-moving, research-based attacks.
Is this attack specific to TanStack or relevant to other packages?
This attack exemplifies a broader trend affecting many open-source packages, especially those relying on GitHub Actions workflows and trust boundaries. The techniques are applicable beyond TanStack and highlight systemic security challenges in modern CI/CD pipelines.
Source: ThorstenMeyerAI.com
