📊 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 used known research to weaponize the supply chain faster than defenses could respond. This highlights the growing sophistication of public research-based attacks.
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 underscores how publicly available security research can be weaponized rapidly, outpacing defenders’ ability to deploy mitigations, and highlights a significant supply-chain risk within open-source ecosystems.
The attack was carried out by an adversary who created a malicious fork of TanStack/router on GitHub, then injected a payload via a crafted commit. The attacker used GitHub Actions’ trust boundary vulnerabilities, including the pull_request_target pattern, cache poisoning across fork and base repositories, and extraction of OIDC tokens from runner memory. These three vulnerabilities, each previously documented in public security research, were chained together to enable the breach.
Specifically, the attacker created a fork on May 10, then committed malicious code that was later included in a pull request targeting TanStack/router. The malicious PR was merged or executed, triggering workflows that allowed the attacker to mint an OIDC token in memory and exfiltrate credentials through an encrypted messaging network, without stealing npm tokens or compromising the publish workflow itself. The attack was detected 28 hours after initial fork creation, as forensic analysis traced the chain of exploits.
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
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.
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.OIDC token security tools
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.
Eyoyo EYH2 Handheld USB 2D Barcode Scanner, Wired Automatic QR Code Scanner PDF417 Data Matrix Bar Code Reader with Long USB Cable for POS Mobile Payment, Convenience Store, Supermarket, Warehouse
Continuous Usage All Day: The EY-H2 USB barcode scanner is designed to always be ready for the next…
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 Public Research-Driven Supply-Chain Attacks
This incident demonstrates how publicly available security research can be weaponized in real-world attacks, enabling sophisticated supply-chain breaches that outpace defensive responses. The attack leveraged three known vulnerabilities, each documented in prior research, to create a chain that compromised a highly security-conscious open-source project. It underscores the importance of re-evaluating trust boundaries and mitigation strategies in the face of rapid, research-based adversary tradecraft, especially as AI and automation accelerate attack speed.
Broader Trends in 2026 Supply-Chain Security Breaches
The TanStack incident is part of a wave of supply-chain compromises in 2026, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. It follows the disclosure of an AI-generated zero-day by Google Threat Intelligence Group on the same day, illustrating a confluence of advanced attack techniques leveraging AI and public research. Prior to this, security research by GitHub Security Lab, Adnan Khan, and StepSecurity had documented vulnerabilities exploited in this attack chain, highlighting a persistent gap between research publication and mitigation deployment.
“The attack exemplifies how publicly available security research becomes attacker tradecraft, enabling breaches faster than defenders can adapt.”
— Thorsten Meyer, researcher
Remaining Questions About Attack Scope and Mitigations
It is still unclear how widespread the immediate impact was beyond TanStack packages, or whether additional compromised packages exist. The full extent of potential downstream exploits remains under investigation. The effectiveness of current mitigations and whether similar chains can be prevented with new security controls is also uncertain, as attackers adapt rapidly.
Future Steps for Open-Source Supply-Chain Security
Security researchers and maintainers are expected to enhance detection of chained vulnerabilities, improve trust boundary controls, and accelerate deployment of mitigations. The incident underscores the need for industry-wide standards to address research-to-tradecraft conversion and to develop real-time monitoring tools. Further forensic analysis will determine if additional packages or projects were affected, and whether new security policies are needed to prevent similar attacks.
Key Questions
How did the attacker exploit the vulnerabilities?
The attacker created a malicious fork, injected code via a crafted commit, exploited trust boundary vulnerabilities in GitHub Actions workflows, and exfiltrated credentials through an encrypted messaging network, chaining three known vulnerabilities.
Are npm tokens or credentials stolen in this attack?
No, the attack did not steal npm tokens. The attacker minted an OIDC token in memory and exfiltrated credentials via an encrypted Session Protocol, avoiding direct theft of stored tokens.
What vulnerabilities were exploited, and were they previously known?
Yes, all three vulnerabilities—pull_request_target misuse, cache poisoning across trust boundaries, and OIDC token extraction—were publicly documented before the attack. Their chaining enabled the breach.
Could this attack happen to other projects?
Yes, any project relying on similar trust boundaries and workflows vulnerable to these known issues could be targeted, especially if mitigations are not rapidly deployed.
What can maintainers do to prevent similar attacks?
Implement stricter trust boundary controls, monitor for suspicious activity in workflows, and accelerate the deployment of mitigations for known vulnerabilities to reduce attack surfaces.
Source: ThorstenMeyerAI.com
