📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
In May 2026, attackers exploited a chain of three publicly known vulnerabilities to compromise TanStack npm packages. The attack leveraged existing research, executed within hours, and bypassed defenses, illustrating the evolving threat landscape.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to publish malicious versions of TanStack npm packages within six minutes, without stealing npm tokens or compromising the publishing workflow directly. This incident underscores how publicly known weaknesses can be weaponized rapidly, even by security-conscious maintainers.
The attack involved chaining three vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory. Each vulnerability was previously documented in security research reports published over the past 12 months, but none alone was sufficient to enable the breach. The attacker created a malicious fork of TanStack/router, inserted a payload via a crafted commit, and used GitHub Actions workflows to authenticate and exfiltrate data, all within six minutes.
Despite the use of two-factor authentication (2FA) and OIDC trusted publishing, the attacker’s chain of exploits allowed them to bypass these defenses by exploiting the trust boundaries between forks, cache, and runtime environments. The breach was detected 28 hours after initial compromise, highlighting the speed at which such attacks can unfold and the difficulty of timely mitigation.
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.
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.OIDC token security tools
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.
Impact of Public Research on Attack Techniques in 2026
This incident demonstrates that the most consequential supply-chain attacks in 2026 are no longer based on novel vulnerabilities but are sophisticated compositions of publicly available research. The rapid execution surpasses defenders’ ability to deploy mitigations, emphasizing the need for proactive security measures and awareness of known weaknesses. It also highlights the importance of understanding trust boundaries within CI/CD pipelines and the risks posed by chaining multiple vulnerabilities.
Broader Supply-Chain Security Challenges in 2026
The May 2026 TanStack incident is part of a wider wave of supply-chain attacks involving over 160 packages compromised during the ongoing Mini Shai-Hulud campaign, which includes high-profile targets like Mistral AI and UiPath. The attack leveraged publicly available research findings from GitHub Security Lab, Adnan Khan, and StepSecurity, illustrating a persistent pattern where attacker tradecraft is rapidly derived from existing disclosures. The incident coincides with the first AI-built zero-day disclosed by Google Threat Intelligence Group, reflecting a broader landscape of AI-augmented offensive capabilities.
“The TanStack attack exemplifies how publicly documented vulnerabilities can be combined into a potent chain, executed faster than defenders can respond.”
— Thorsten Meyer
Remaining Uncertainties About Attack Scope and Detection
It is still unclear how many other packages or projects might have been similarly compromised using this chain of vulnerabilities. The full extent of the attacker’s access and whether other payloads were deployed remains unconfirmed. Additionally, the exact timeline for the attacker’s initial foothold and the potential for subsequent exploitation are still under investigation.
Future Mitigations and Monitoring Strategies
Security researchers and maintainers are expected to review trust boundaries, improve CI/CD security practices, and monitor for similar chaining patterns. Organizations should also audit their workflows for the presence of these vulnerabilities and consider deploying enhanced detection for suspicious activity within GitHub Actions and package publishing processes. Ongoing investigations will determine if further breaches occurred or if additional vulnerabilities are being exploited.
Key Questions
How did the attacker bypass security measures like 2FA?
The attacker exploited trust boundaries within the CI/CD pipeline, using publicly documented vulnerabilities to chain exploits that did not require stealing credentials directly from the publisher.
Are other npm packages at risk from similar attacks?
Yes, any package with similar trust boundaries or workflow configurations could be vulnerable if the same chain of vulnerabilities is present. Vigilance and review of security practices are recommended.
What can maintainers do to prevent such attacks?
Implement stricter access controls, monitor for suspicious commits, review trust boundaries within workflows, and stay updated on public research related to pipeline security.
Is this incident linked to AI-based attack tools?
While the attack leveraged publicly available research, it coincided with the disclosure of an AI-built zero-day, underscoring the increasing role of AI in offensive security operations.
Source: ThorstenMeyerAI.com
