📊 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. The attack was executed rapidly, leveraging published research to bypass defenses. This incident highlights the growing challenge of defense lag against well-understood attack methods.
On May 11, 2026, attackers published 84 malicious versions of TanStack npm packages within six minutes, exploiting a chain of three publicly documented vulnerabilities in GitHub Actions and npm workflows. The attack leveraged trusted relationships and existing research, demonstrating a sophisticated use of known security flaws.
The attack involved creating a malicious fork of the TanStack/router repository, injecting a payload via a crafted commit, and exploiting GitHub Actions workflows to exfiltrate credentials without stealing npm tokens or compromising the publish process directly. The attacker used a forged author identity and manipulated the pull_request_target pattern, which had been publicly documented as dangerous years earlier.
Three vulnerabilities formed the chain: the pull_request_target ‘Pwn Request’ pattern (documented by GitHub Security Lab), cache poisoning across fork-base trust boundaries (documented by Adnan Khan in May 2024), and OIDC token extraction from GitHub Actions runner memory (documented by StepSecurity in March 2025). Each was necessary but not sufficient alone; their combination enabled the breach.
The incident exemplifies how publicly known attack techniques can be combined into a potent chain, executed faster than defenses can adapt, highlighting the challenge of closing the gap between research and operational mitigation.
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.
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.
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.
Incident Response Team Mug – Cybersecurity Alert Design – 11 oz Ceramic
CYBERSECURITY DESIGN: Features bold 'Incident Response Team' typography surrounded by alert symbols, shield icons, padlocks, and intricate circuit…
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 for Supply Chain Security and Defense Speed
This incident underscores the risk posed by publicly documented vulnerabilities when combined into attack chains, especially in complex CI/CD environments. It reveals that attacker tradecraft is increasingly composed of well-understood research, executed faster than security teams can deploy mitigations. The attack’s reliance on known flaws emphasizes the need for rapid, systemic defense strategies and continuous security review of trusted workflows in open-source and enterprise ecosystems.
Historical and Technical Background of the Attack Chain
The May 2026 TanStack breach is part of a broader wave of supply chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. The attack built upon three key research findings published over the previous year: the dangerous use of pull_request_target workflows, cache poisoning techniques, and OIDC token extraction from CI runners. These vulnerabilities had been publicly documented and analyzed, but their combination into an attack chain was unprecedented in terms of speed and impact.
On May 10, 2026, the attacker created a malicious fork of the TanStack/router repository, inserted a payload via a crafted commit, and then used a pull request to trigger workflows that exfiltrated credentials. The attack exploited trust boundaries across the CI/CD pipeline, culminating in rapid package compromise on May 11. This sequence demonstrates how well-understood vulnerabilities can be weaponized in a coordinated, high-speed attack.
“The TanStack incident exemplifies how publicly available research can be combined into an effective attack chain, executed faster than defenses can respond.”
— Thorsten Meyer, Security Researcher
Remaining Unknowns About the Attack Chain and Impact
While the technical chain has been reconstructed in detail, it is not yet clear how widespread the impact was beyond the compromised packages. The full extent of the attacker’s access and whether additional malicious activities occurred remain under investigation. The long-term implications for other packages and workflows using similar trust boundaries are still being assessed.
Next Steps for Detection, Mitigation, and Industry Response
Security teams are expected to review and patch CI/CD workflows, especially those involving pull_request_target patterns and OIDC configurations. Increased monitoring for similar attack chains and public research-based exploits is anticipated. The incident also prompts a call for faster, more integrated deployment of mitigations against known vulnerabilities, along with heightened awareness of the risks inherent in trust boundary crossings in software supply chains.
Key Questions
How did the attacker execute the breach so quickly?
The attacker combined three publicly documented vulnerabilities into a chain, executing them within minutes by exploiting trust boundaries in CI/CD workflows and using forged identities, which allowed rapid exfiltration of credentials.
Were npm tokens stolen in this attack?
No, the attack did not involve stealing npm tokens. Instead, the attacker minted an OIDC token in memory and exfiltrated credentials via the encrypted Session Protocol, avoiding direct token theft.
What vulnerabilities were exploited in this attack?
The attack chain involved the pull_request_target ‘Pwn Request’ pattern, cache poisoning across fork-base trust boundaries, and OIDC token extraction from CI runner memory. All three were publicly documented prior to the incident.
What should open-source maintainers do now?
Maintainers should review their CI/CD configurations, especially pull request workflows and trust boundary policies. Applying stricter controls and monitoring for known attack techniques is recommended.
Is this type of attack likely to happen again?
Yes, given that the vulnerabilities are publicly known and can be combined into effective attack chains, similar incidents may occur unless defenses are rapidly improved and mitigations are widely deployed.
Source: ThorstenMeyerAI.com
