📊 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. The attack was rapid, weaponized existing research, and highlights the challenges in defending against fast-moving supply-chain threats.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages, using existing research to rapidly weaponize the attack before defenses could respond. This incident underscores the growing challenge of defending against supply-chain attacks that leverage well-known flaws in complex, interconnected systems.
The attack involved the publication of 84 malicious package versions across 42 TanStack npm packages within six minutes. The attacker used the GitHub Actions OIDC trusted-publisher binding to authenticate, without stealing npm tokens. Instead, the attacker minted an in-memory OIDC token, exfiltrating credentials via the encrypted Session Protocol network, which lacked attacker-controlled C&C infrastructure.
Forensic analysis revealed that three vulnerabilities, each previously documented in public security research, were chained together to enable the attack. These are: the pull_request_target “Pwn Request” pattern (documented by GitHub Security Lab), cache poisoning across fork and base trust boundaries (by Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runner memory (by StepSecurity, March 2025). Each vulnerability was necessary but not sufficient alone; their combination created the attack surface.
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
npm package security 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.OIDC token protection tools
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 Publicly Known Vulnerabilities in Supply-Chain Attacks
This incident demonstrates that the most consequential supply-chain attacks in 2026 are not based on novel exploits but are composed of publicly available research, executed faster than defenders can deploy mitigations. It highlights the critical need for faster, more integrated security responses and emphasizes that the attack surface is increasingly defined by known vulnerabilities chained together.
Historical Background of the Vulnerabilities and Attack Environment
The attack builds upon three separate research findings published between March 2024 and March 2025, each describing a specific vulnerability in the GitHub Actions ecosystem. The first, by GitHub Security Lab, detailed the dangerous pull_request_target pattern. The second, by Adnan Khan, explained cache poisoning across trust boundaries. The third, by StepSecurity, described OIDC token extraction from runner memory. The attack on TanStack occurred within a broader wave of supply-chain compromises involving over 160 packages, part of the ongoing Mini Shai-Hulud campaign, illustrating the systemic nature of these threats.
“The TanStack incident exemplifies how publicly documented vulnerabilities are now being combined into sophisticated attack chains, executed faster than defenders can adapt.”
— Thorsten Meyer
Unresolved Aspects of the Chain and Defense Gaps
While the forensic timeline clarifies the sequence of events, it remains unclear how widespread the initial access was beyond the TanStack incident, and whether other packages or ecosystems have been similarly targeted using the same chain. Additionally, the effectiveness of current mitigations against such chained vulnerabilities is still under assessment, and the full scope of attacker capabilities remains uncertain.
Next Steps in Mitigation and Monitoring
Security teams are expected to review and update CI/CD security practices, focusing on mitigating known vulnerabilities like pull_request_target abuse, cache poisoning, and in-memory token extraction. Increased monitoring for similar attack patterns and faster deployment of mitigations are anticipated. Further forensic investigations will determine if other packages or ecosystems have been compromised using similar chains, and industry-wide efforts are likely to accelerate to address these systemic vulnerabilities.
Key Questions
How did the attacker manage to exploit these vulnerabilities so quickly?
The attacker combined three publicly documented vulnerabilities into a chain, which allowed rapid weaponization and execution within minutes, exploiting the fact that these flaws are well known but not yet fully mitigated in the ecosystem.
Were any npm tokens stolen during the 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 network.
What does this incident reveal about the security of open-source supply chains?
It underscores that publicly documented vulnerabilities can be combined into effective attack chains, emphasizing the need for faster mitigation deployment and more resilient security practices in open-source ecosystems.
Are similar attacks likely to happen again?
Yes, given the pattern of chaining known vulnerabilities and the speed at which attackers can weaponize published research, such attacks are likely to recur unless systemic security improvements are made.
What can maintainers and organizations do to protect themselves?
They should regularly review and apply security patches for known vulnerabilities, implement stricter CI/CD controls, monitor for suspicious activity, and adopt defense-in-depth strategies to mitigate chained attack vectors.
Source: ThorstenMeyerAI.com
