📊 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 in TanStack npm packages, enabling a sophisticated supply chain attack. The incident highlights the speed at which public research can be weaponized.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages, resulting in the publication of 84 malicious versions within six minutes. The attack was carried out via GitHub Actions and did not involve stolen tokens, but rather the in-memory exfiltration of credentials through a chain of known flaws. This incident exemplifies how publicly available security research can be rapidly weaponized in supply chain attacks, raising concerns over the pace of defense deployment.
The attack originated from a malicious fork of TanStack/router created on May 10, 2026, by a GitHub user using a deliberately obscured identity. The attacker inserted a large JavaScript payload into the fork, which was later used in a pull request opened on May 11, 2026, triggering the malicious workflow. The attacker exploited three known vulnerabilities: the pull_request_target “Pwn Request” pattern (documented by GitHub Security Lab), cache poisoning across trust boundaries (documented by Adnan Khan), and extraction of OIDC tokens from GitHub Actions runners (documented by StepSecurity). Each vulnerability alone was insufficient, but chained together they enabled the attacker to mint an OIDC token in memory and exfiltrate credentials via an encrypted messaging network, without stealing npm tokens or compromising the publish workflow itself.
The incident was part of a broader wave of supply chain compromises, affecting over 160 packages, including prominent entities like Mistral AI and UiPath. Despite the TanStack team’s security measures, including 2FA and OIDC trusted publishing, the chain of vulnerabilities allowed the attacker to bypass defenses. The attack was detected 28 hours after the initial fork creation, highlighting the rapidity of the breach and the challenge for defenders to keep pace with publicly available exploit techniques.
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
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.
Python Cybersecurity Automation Tips – Efficient security monitoring and penetration testing automation using scripts and tools – (Japanese Edition)
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 products
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 in Supply Chain Attacks
This incident underscores a systemic issue: publicly available security research can be rapidly weaponized, outpacing defenders’ ability to deploy mitigations. The attack demonstrates that the most impactful supply chain compromises in 2026 are not based on novel exploits but on sophisticated combinations of existing vulnerabilities. For open-source maintainers and enterprise users, this highlights the need for continuous, layered security strategies and faster response mechanisms to address known issues before they are exploited at scale.
Public Research and the 2026 Supply Chain Surge
The May 2026 TanStack incident is part of a broader wave of supply chain attacks that began earlier in the year, involving over 160 compromised packages across multiple ecosystems. Notably, three vulnerabilities—related to GitHub Actions trust boundaries, cache poisoning, and token extraction—were all documented publicly between March 2025 and May 2024. These findings became attacker tradecraft within a year, illustrating how open-source security research can inadvertently facilitate attacks when not accompanied by rapid mitigation deployment. The incident also coincides with the same day as the Google Threat Intelligence Group’s disclosure of an AI-built zero-day, emphasizing the convergence of offensive capabilities.
“The TanStack attack exemplifies how publicly documented vulnerabilities can be chained into a sophisticated supply chain breach, executed faster than defenders can respond.”
— Thorsten Meyer
Remaining Uncertainties About the Attack Chain
Details about the attacker’s full operational infrastructure and whether additional vulnerabilities were exploited beyond the three documented remain unclear. While forensic analysis confirms the chain of vulnerabilities, the precise timing and scope of the exfiltration and subsequent malicious activities are still under investigation. It is also unknown whether similar chains have been used in other recent supply chain attacks or if this was a unique case of rapid weaponization.
Next Steps for Defense and Mitigation Strategies
Security researchers and open-source maintainers are expected to prioritize patching known vulnerabilities and reviewing trust boundaries within CI/CD pipelines. Developers should enhance monitoring for suspicious activity, especially around pull request workflows and token exfiltration. Industry-wide, there will likely be increased emphasis on rapid response frameworks and sharing of attack patterns to mitigate the risk of similar chains being exploited in future incidents. Ongoing forensic analysis will continue to clarify the attack scope and whether other packages or ecosystems are similarly vulnerable.
Key Questions
How did the attacker exploit the vulnerabilities without stealing npm tokens?
The attacker minted an OIDC token in memory during the GitHub Actions workflow and exfiltrated credentials via an encrypted messaging network, avoiding the need to steal npm tokens or compromise the publish process directly.
Are these vulnerabilities still present in other repositories?
Since these vulnerabilities are publicly documented, it is likely they exist in other projects that have not yet applied mitigations. Developers should review their CI/CD pipelines for similar trust boundary issues.
What can maintainers do to prevent similar attacks?
Maintain security reviews of trust boundaries, avoid using pull_request_target in untrusted workflows, and implement stricter monitoring for suspicious commits or activity within forks.
Is this attack indicative of a new trend in supply chain compromises?
Yes, it exemplifies how publicly available research can be rapidly weaponized, making the attack surface more about composition of known flaws than novel exploits.
Source: ThorstenMeyerAI.com
