📊 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 known vulnerabilities to compromise TanStack npm packages within six minutes. The attack used existing research, highlighting the speed at which public research can be weaponized.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes, demonstrating how existing security research can be weaponized rapidly and at scale.
The attack involved a malicious actor creating a fork of TanStack/router, injecting a payload via a crafted commit, and leveraging a chain of three known vulnerabilities—PR fork code crossing trust boundaries, cache poisoning across fork-base trust, and OIDC token extraction from GitHub Actions runners. These vulnerabilities, each documented in public security research prior to the incident, were combined by the attacker to bypass multiple defenses without stealing any npm tokens or compromising the publish workflow directly.
The attacker used a fabricated author identity, created a malicious fork, and triggered a pull request that exploited the ‘pull_request_target’ pattern, enabling code injection into the main repository. The attacker then exfiltrated credentials via in-memory OIDC tokens, with no attacker-controlled command-and-control infrastructure involved. The attack was detected within 28 hours, and detailed forensic analysis has been published by security researchers and GitHub.
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.
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.
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.
Tricks for enterprise-level security monitoring and vulnerability assessment in Python: Using advanced tools and frameworks for security auditing and penetration testing (Japanese Edition)
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-Driven Supply Chain Attacks
This incident exemplifies how publicly available security research can be combined into sophisticated attack chains, enabling rapid exploitation that outpaces defensive deployment. It underscores the operational risks faced by open-source projects and enterprise supply chains, especially as AI-augmented attack techniques evolve. The attack also highlights the importance of understanding trust boundaries within CI/CD pipelines and the need for proactive mitigation strategies.
Pre-Existing Research Enabled the Attack Chain
Prior to the TanStack incident, three key vulnerabilities had been publicly documented: the ‘pull_request_target’ code crossing trust boundaries (GitHub Security Lab, 2021), cache poisoning across fork and base repositories (Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runners (StepSecurity, March 2025). Each was considered a separate security concern, but their combination in this attack demonstrated a new level of operational risk. The incident occurred amid a wave of supply-chain compromises affecting over 160 packages, including prominent firms like Mistral AI and UiPath, part of the ongoing Mini Shai-Hulud campaign.
“The TanStack attack exemplifies how existing security research can be weaponized in real-time, exposing vulnerabilities in supply-chain defenses that are slow to adapt.”
— Thorsten Meyer
Remaining Uncertainties About Attack Extent and Mitigations
While the technical chain has been reconstructed and analyzed, it remains unclear how many other projects may have been similarly compromised using this method, or whether additional undisclosed vulnerabilities were exploited. The full scope of the attack’s impact on other npm packages and ecosystems is still being assessed.
Future Steps for Defense and Monitoring
Security teams and open-source maintainers are expected to review and strengthen trust boundary controls, implement stricter code review processes, and monitor for signs of similar attack patterns. GitHub and npm are likely to update their security advisories and introduce new mitigations to prevent chain exploitation of publicly documented vulnerabilities. Ongoing forensic investigations will clarify the full scope and recovery strategies.
Key Questions
How did the attacker exploit publicly known vulnerabilities?
The attacker combined three publicly documented vulnerabilities—PR code crossing trust boundaries, cache poisoning, and OIDC token extraction—to craft a chain that bypassed multiple defenses and exfiltrated credentials without stealing tokens or directly compromising the publish workflow.
What does this attack reveal about open-source security?
It highlights that publicly available security research can be weaponized rapidly, emphasizing the need for proactive mitigation, layered defenses, and continuous monitoring rather than relying solely on patching known issues.
Are npm packages still safe after this incident?
While the incident demonstrates a significant risk, ongoing efforts by maintainers and platform providers aim to improve security controls. Users should stay informed about advisories and adopt best practices for supply-chain security.
Will this lead to new security standards for CI/CD pipelines?
It is likely. The incident underscores the importance of trust boundary controls, code review processes, and environment isolation, which may be incorporated into future security standards and best practices.
Source: ThorstenMeyerAI.com
