📊 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 within six minutes. This incident exemplifies how public security research can enable sophisticated supply-chain attacks.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes. This incident involved the use of publicly available security research to craft a sophisticated supply-chain attack, highlighting the speed at which attacker tradecraft can evolve faster than defense deployment. The attack targeted the TanStack/router package, which is widely used in JavaScript development, raising concerns about supply-chain security in open-source ecosystems.
The attack was carried out by creating a malicious fork of the TanStack/router repository, then injecting a payload through a pull request that triggered a series of GitHub Actions workflows. The attacker, using a fabricated identity, inserted malicious code into the fork on May 10, 2026, and later opened a pull request on May 11, which triggered the attack chain.
Key vulnerabilities exploited included the pull_request_target ‘Pwn Request’ pattern, cache poisoning across trust boundaries in GitHub Actions, and OIDC token extraction from runner memory. All three vulnerabilities had been publicly documented prior to the attack: by GitHub Security Lab in 2022, Adnan Khan in May 2024, and StepSecurity in March 2025. Each vulnerability alone was insufficient, but combined, they enabled the attacker to mint an OIDC token, exfiltrate credentials, and publish malicious package versions in a six-minute window.
The incident was detected 28 hours after initial fork creation, demonstrating rapid attack progression. The attack did not involve theft of npm tokens but relied on exploiting trust boundaries within the CI/CD pipeline, specifically the trust in GitHub Actions workflows and the package publishing process.
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
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.npm package vulnerability scanner
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.
The Android Malware Handbook: Detection and Analysis by Human and Machine
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 Chain-Exploited Public Vulnerabilities
This incident underscores a fundamental shift in software supply-chain security: publicly documented vulnerabilities, when chained together, can be weaponized swiftly and effectively. The attack exemplifies how attacker tradecraft now leverages existing research, making defenses slower than the pace of offensive innovation. For open-source maintainers and enterprise users, this highlights the importance of understanding and mitigating known vulnerabilities across trust boundaries, especially in CI/CD pipelines.
Furthermore, the incident signals that the most consequential supply-chain attacks in 2026 are less about novel exploits and more about the composition of existing vulnerabilities. This challenges the traditional focus on discovering new flaws alone, emphasizing the need for comprehensive mitigation strategies that address the entire attack surface.
Public Research as an Enabler for Supply-Chain Attacks
The May 2026 attack on TanStack is part of a broader wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign, which also targeted organizations like Mistral AI, UiPath, and Squawk. Prior to the incident, researchers had publicly documented three key vulnerabilities that, when combined, create a reliable attack chain:
- The pull_request_target ‘Pwn Request’ pattern (documented by GitHub Security Lab in 2022)
- GitHub Actions cache poisoning across trust boundaries (Adnan Khan, May 2024)
- OIDC token extraction from runner memory (StepSecurity, March 2025)
Each of these vulnerabilities was known and published, but their combined use in an attack was unprecedented at scale. The incident demonstrates how attacker tradecraft is compressed from research to execution, often outpacing deployment of mitigations.
“The TanStack incident exemplifies how publicly available security research can be weaponized rapidly, turning known vulnerabilities into a potent attack chain.”
— Thorsten Meyer, security researcher
Unconfirmed Aspects of the Attack Chain
While the attack chain has been reconstructed based on forensic analysis, some details remain unclear, including the full extent of exfiltrated data and whether additional vulnerabilities or attack vectors were involved. The precise timeline of the attacker’s actions post-exfiltration is still under investigation, and the full scope of affected packages beyond TanStack has not been publicly disclosed.
Mitigation Strategies and Industry Response
Security teams are expected to review and strengthen CI/CD security practices, especially around trust boundaries in automation workflows. Open-source maintainers are advised to audit their repositories for similar vulnerabilities and adopt mitigations such as stricter access controls and improved monitoring. Industry-wide, there will likely be increased emphasis on vulnerability chaining analysis and rapid response protocols to address the speed of modern supply-chain attacks.
Further investigations are ongoing to assess the full impact and develop targeted mitigations, with updates anticipated from GitHub and affected organizations in the coming weeks.
Key Questions
How did the attacker exploit the vulnerabilities so quickly?
The attacker chained publicly documented vulnerabilities, exploiting trust boundaries within GitHub Actions workflows and the package publishing process, enabling rapid exfiltration and package compromise within six minutes after initial fork creation.
Were any npm tokens stolen during the attack?
No, the attack did not involve theft of npm tokens. The attacker minted an OIDC token in memory and exfiltrated credentials via a secure messaging network, avoiding direct token theft.
What can maintainers do to prevent similar attacks?
Maintainers should audit their CI/CD workflows, restrict trust boundaries, and monitor for suspicious activity. Applying stricter access controls and staying updated on known vulnerabilities can reduce attack surface risks.
Is this type of attack likely to happen again?
Yes, given the availability of public research on security vulnerabilities and the attacker’s ability to chain them, similar attacks are likely unless defenses evolve to address the entire attack surface.
Source: ThorstenMeyerAI.com
