📊 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 documented vulnerabilities to compromise TanStack npm packages within six minutes. The attack leveraged known flaws in GitHub Actions and trust boundaries, illustrating the rapid pace of AI-augmented supply-chain attacks.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to publish malicious versions of TanStack npm packages within six minutes, without stealing npm tokens or compromising the publish workflow.
The attack involved chaining three known vulnerabilities: the pull_request_target “Pwn Request” pattern, GitHub Actions cache poisoning across trust boundaries, and OIDC token extraction from runner memory. These vulnerabilities, each documented in security research before 2026, were combined by the attacker to breach the TanStack release process.
The attacker created a malicious fork of TanStack/router on May 10, then injected a payload via a crafted commit. On May 11, the attacker triggered a pull request that exploited the trust boundaries within GitHub Actions workflows, culminating in the exfiltration of an OIDC token in memory. This allowed the attacker to publish malicious package versions directly to npm, without compromising the npm registry or stealing tokens.
The incident exemplifies how publicly known vulnerabilities can be chained to produce sophisticated attacks faster than defenses can respond. The attack occurred on the same day as the first AI-built zero-day disclosure by Google Threat Intelligence Group, underscoring the convergence of AI and supply-chain threats.
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 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.GitHub Actions security monitoring
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 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.
Implications of Public Research-Driven Supply-Chain Attacks
This incident demonstrates that the most significant supply-chain security breaches in 2026 are no longer driven by novel vulnerabilities but by the rapid combination of publicly available research. Attackers are weaponizing known flaws at a pace that outstrips the deployment of mitigations, emphasizing the need for faster response and more resilient security architectures in open-source ecosystems.
The attack on TanStack, a reputable open-source maintainer, highlights how even well-secured projects with multi-factor authentication and trusted publishing can be compromised through chained vulnerabilities. This raises concerns about the entire supply chain’s vulnerability to similar multi-vector, AI-augmented attacks, which could affect countless other projects and organizations relying on npm.
Public Research and the Evolution of Supply-Chain Attacks in 2026
Throughout 2026, multiple security research findings have exposed vulnerabilities in CI/CD pipelines, trust boundaries, and dependency management. Notably, in May 2024, Adnan Khan documented cache poisoning across fork and base trust boundaries, and in March 2025, StepSecurity described OIDC token extraction from GitHub Actions runners. These findings laid the groundwork for the May 11 attack, which combined these known flaws into a potent chain.
The incident is part of a broader wave of supply-chain compromises, including over 160 packages affected during the ongoing Mini Shai-Hulud campaign, which involves multiple organizations and AI-augmented exploits. The attack timeline shows how attacker tradecraft has compressed from months or years into days, enabled by AI-assisted research and automation.
“The TanStack incident exemplifies how publicly documented vulnerabilities are rapidly weaponized, creating an attack surface that outpaces defensive deployment.”
— Thorsten Meyer
Unresolved Questions About Attack Scope and Mitigations
It remains unclear how widespread the impact is beyond the compromised TanStack packages, and whether additional, undiscovered vulnerabilities facilitated the attack. The full extent of the attacker’s access and potential further exploits are still under investigation.
Additionally, the speed at which defenders can deploy effective mitigations against chained, research-based attacks remains uncertain, highlighting a gap between attacker capabilities and defensive responses.
Next Steps for Detection, Response, and Prevention
Organizations relying on CI/CD pipelines should review and strengthen trust boundary controls, especially around pull request workflows and runner memory protections. Increased monitoring for suspicious fork activity and anomalous commits is recommended.
Security teams are expected to analyze the attack chain further, develop targeted mitigations, and share best practices for defending against chained vulnerabilities. The incident also emphasizes the need for faster integration of security research into operational defenses and continuous threat intelligence updates.
Key Questions
How did the attacker manage to publish malicious packages without stealing npm tokens?
The attacker exploited a chain of vulnerabilities to exfiltrate an OIDC token from memory during workflow execution, allowing them to authenticate as a trusted publisher without stealing tokens.
Are other open-source projects at similar risk from this kind of attack?
Yes, any project using automated workflows with trust boundaries similar to TanStack is potentially vulnerable if they have not implemented mitigations against chained, publicly documented vulnerabilities.
What measures can organizations take to prevent such attacks?
Strengthening trust boundary controls, monitoring for suspicious activity, limiting fork and PR trust, and applying security patches for known vulnerabilities are critical steps.
Is this attack an isolated incident or part of a broader campaign?
This attack is part of the ongoing Mini Shai-Hulud campaign, which has affected over 160 packages and involves multiple threat actors leveraging AI-augmented tradecraft.
Source: ThorstenMeyerAI.com
