📊 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 within six minutes. The attack highlights how public research can be weaponized faster than defenses can respond, raising concerns about supply-chain security.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages within six minutes, using a sophisticated combination of known security flaws. This incident underscores how publicly available research can be weaponized rapidly, outpacing defensive measures and illustrating the evolving threat landscape in software supply chains.
The attack involved the publication of 84 malicious npm package versions across 42 TanStack packages, executed via a compromised GitHub Actions workflow. The attacker created a fork of the TanStack/router repository, inserted malicious code, and triggered a pull request that executed within the trusted CI/CD pipeline, leading to package compromise.
Key to the attack was the chaining of three vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across trust boundaries, and extraction of OIDC tokens from GitHub Actions runner memory. Each vulnerability had been publicly documented before the incident, with the most recent research published 12 months prior. The attacker combined these known issues to breach the supply chain, illustrating how public research can be weaponized in offensive campaigns.
Despite the TanStack team’s security measures—including 2FA and OIDC trusted publishing—the chain of vulnerabilities enabled the breach without any single flaw being sufficient on its own. The attack was executed within hours of the vulnerabilities being publicly documented, demonstrating the speed at which attacker tradecraft can evolve from research to operational tool.
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
Never Miss a Thing with 2K Clarity! Plug-in Indoor Security Camera with Motion Detection for Continuous Monitoring. Easy Tabletop Setup, Secure via Cloud or SD Card.
[2K Day & Night Clarity] Plug in for continuous 2K HD recording. See clear details day or night.
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.
Accelerate DevOps with GitHub: Enhance software delivery performance with GitHub Issues, Projects, Actions, and Advanced Security
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.
Barcode Scanner with Stand, USB Wired Inventory 2D 1D QR Code Scanner for Computer POS MAC with Automatic Screen Scanning, Handheld CMOS Image Bar Code Reader for Warehouse Library Supermarket
Plug and play, Easy Use(Not compatible with Square system): Anyeast USB barcode scanner does not require installation of…
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 Supply-Chain Security
This incident exemplifies how publicly available security research can be rapidly weaponized by malicious actors, creating a new paradigm in supply-chain attacks. The fact that the attack relied on chaining multiple documented vulnerabilities highlights the need for proactive, layered defenses and continuous monitoring of known issues. It raises questions about the adequacy of current mitigation strategies and underscores the urgency for the ecosystem to adapt faster than threat actors can leverage open-source research.
Public Research and the Evolution of Supply-Chain Attacks
Over the past year, multiple vulnerabilities relevant to CI/CD pipelines and package management have been publicly documented: the pull_request_target pattern (by GitHub Security Lab, 2021), cache poisoning (by Adnan Khan, May 2024), and OIDC token extraction (by StepSecurity, March 2025). These findings laid the groundwork for the May 2026 attack, which combined them into a chain that exploited trust boundaries within the software supply chain.
The attack occurred during a period of heightened awareness about supply-chain risks, following disclosures of AI-built zero-days and ongoing campaigns targeting open-source ecosystems. The TanStack incident is part of a broader wave of supply-chain compromises affecting over 160 packages across multiple vendors, illustrating the systemic nature of the threat.
“The TanStack attack demonstrates how publicly available research can be weaponized at scale, emphasizing the need for faster mitigation deployment.”
— Thorsten Meyer, security researcher
Unclear Aspects of the Ongoing Investigation
While the forensic analysis confirms the chain of vulnerabilities used, the full extent of the attacker’s access and any additional malicious activities remain under investigation. It is not yet confirmed whether other repositories or packages were similarly compromised, or if the attacker exploited additional, undisclosed vulnerabilities.
Future Mitigation Strategies and Ecosystem Responses
Security teams are expected to enhance detection and mitigation measures, including stricter review of pull requests, improved CI/CD security, and faster patch deployment. The incident prompts a reevaluation of trust boundaries and the need for proactive security practices across open-source projects. Ongoing research and community efforts aim to develop better defenses against chained vulnerabilities and supply-chain attacks.
Key Questions
How did the attacker exploit the vulnerabilities so quickly?
The attacker chained publicly documented vulnerabilities that each required specific conditions to exploit, enabling rapid, automated attack execution once the chain was assembled.
Were any npm tokens stolen during the attack?
No, the attack did not involve theft of npm tokens. Instead, the attacker minted an OIDC token in memory and exfiltrated credentials via the Session Protocol, a secure messaging network.
What can open-source maintainers do to prevent similar attacks?
Implement stricter code review processes, monitor for known attack patterns, and adopt security best practices for CI/CD workflows. Also, stay informed about public research that could be weaponized.
Is this incident unique or part of a broader trend?
This incident is part of a broader wave of supply-chain compromises involving multiple packages and vendors, driven by the rapid weaponization of publicly available research.
Source: ThorstenMeyerAI.com
