📊 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. The attack used publicly documented flaws to bypass defenses, highlighting the threat of rapid, research-based exploits.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise multiple TanStack npm packages within minutes. The attack was carried out via GitHub Actions workflows using trusted-publisher bindings, without stealing npm tokens. This incident exemplifies how publicly known security flaws can be combined for sophisticated supply-chain attacks.
The attack involved creating a malicious fork of the TanStack/router repository, then injecting a payload through a crafted commit. The attacker used a forged author identity and leveraged a malicious pull request targeting the main branch, triggering the GitHub Actions workflow configured for package publishing. The attacker minted an OIDC token in memory and exfiltrated credentials via an encrypted messaging protocol, without compromising the npm publish process itself.
The chain of vulnerabilities includes:
- The pull_request_target “Pwn Request” pattern, documented by GitHub Security Lab as a dangerous pattern years before.
- GitHub Actions cache poisoning across fork and base trust boundaries, detailed by Adnan Khan in May 2024.
- Extraction of OIDC tokens from GitHub Actions runner memory, documented by StepSecurity in March 2025.
All three vulnerabilities are necessary for the attack; none alone would suffice. The attack leverages the trust chain across different components, exploiting publicly known flaws in a coordinated manner.
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.
GitHub Actions security monitoring tools
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.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.
Software Supply Chain Security: Securing the End-to-End Supply Chain for Software, Firmware, and Hardware
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 Exploited in Supply-Chain Attack
This incident demonstrates that publicly available security research can be weaponized rapidly, outpacing defenders’ ability to deploy mitigations. It underscores the importance of re-evaluating trust boundaries and security assumptions in CI/CD pipelines, especially in open-source ecosystems. The attack also highlights the need for continuous review of well-known vulnerabilities and the risks of chaining multiple issues.
Broader Trends in 2026 Supply-Chain Security Incidents
The TanStack attack is part of a larger wave of supply-chain compromises in May 2026, affecting over 160 packages across multiple organizations, including Mistral AI and UiPath. The incident coincides with the disclosure of the first AI-generated zero-day by Google Threat Intelligence Group, illustrating a convergence of AI-augmented offensive techniques and well-documented vulnerabilities. The research-to-tradecraft compression—where public research becomes attacker tradecraft—has accelerated, making such attacks more prevalent and faster to execute.
Prior to this, vulnerabilities such as the pull_request_target pattern, cache poisoning, and OIDC token extraction had been documented for over a year, but their combined exploitation was unprecedented. The incident reveals that the most significant supply-chain risks in 2026 are less about novel exploits and more about the rapid chaining of existing, well-understood vulnerabilities.
“The TanStack incident exemplifies how publicly documented vulnerabilities can be combined into sophisticated supply-chain attacks, often faster than defenders can respond.”
— Thorsten Meyer
Remaining Questions About the Attack Chain and Impact
While the technical chain has been reconstructed, the full extent of the compromise, including potential lateral movements or data exfiltration beyond package publishing, remains under investigation. It is also unclear how widespread the malicious payloads are within the compromised packages and whether other repositories or organizations are affected beyond the publicly identified incident.
Future Steps for Detection, Mitigation, and Prevention
Security teams will likely prioritize revising trust assumptions in CI/CD workflows, especially regarding fork handling and pull request targeting. Increased monitoring for chain-reaction vulnerabilities and rapid deployment of mitigations are expected. Additionally, the incident underscores the need for improved security awareness around publicly documented vulnerabilities and their potential for chaining into complex attacks. Ongoing forensic analysis will determine the full scope and any further malicious activity.
Key Questions
How did the attacker bypass GitHub’s security protections?
The attacker used a forged author identity and exploited known vulnerabilities—pull_request_target, cache poisoning, and OIDC token extraction—chained together to execute the attack without stealing tokens or compromising the publish workflow directly.
Are other npm packages or projects at similar risk?
Yes, any project utilizing similar CI/CD configurations and trust boundaries may be vulnerable to similar chaining attacks, especially if they rely on publicly documented vulnerabilities without additional hardening measures.
What can maintainers do to prevent such attacks?
Implement stricter review processes for forks, avoid trusting pull request target workflows without additional verification, and monitor for known vulnerability chains. Continuous security assessments and hardened CI/CD pipelines are essential.
Is this attack technique new?
No, the attack leverages publicly documented vulnerabilities that have been known for over a year. The novelty lies in chaining these known issues into a high-impact, automated supply-chain attack.
Source: ThorstenMeyerAI.com
