📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
An attacker exploited a chain of three publicly known vulnerabilities to compromise TanStack npm packages within six minutes. The attack highlights how fast offensive tradecraft can outpace defenses, especially when built from public research.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes, demonstrating how publicly available research can be weaponized faster than defenses can respond. This incident underscores the growing threat of AI-augmented cyber offense leveraging known security flaws.
The attack involved the publication of 84 malicious package versions across 42 TanStack npm modules, executed via a compromised GitHub Actions workflow. The attacker used a trusted-publisher binding through GitHub’s OIDC authentication to exfiltrate credentials without stealing npm tokens or compromising the publish process itself. The breach was enabled by a chain of three vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across trust boundaries, and OIDC token extraction from runner memory. All three vulnerabilities had been publicly documented in security research prior to the attack, with the latest being from March 2025.
Forensic analysis shows the attacker created a malicious fork on May 10, 2026, inserted a payload via a crafted commit, and then opened a pull request on May 11, which triggered the malicious package publication. The entire operation was completed within six minutes, illustrating the speed at which attacker tradecraft can be deployed using publicly available research findings.
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.
npm package security scanner
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
Accelerate DevOps with GitHub: Enhance software delivery performance with GitHub Issues, Projects, Actions, and Advanced Security
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.OIDC token 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.
Software Supply Chain Security: Securing the End-to-End Supply Chain for Software, Firmware, and Hardware
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 demonstrates that the most damaging supply-chain attacks in 2026 are composed of publicly known vulnerabilities assembled rapidly into effective exploits. It highlights the challenge for defenders: published security research becomes attacker tradecraft almost immediately, often outpacing mitigation deployment. The attack also shows how AI tools can accelerate the composition and deployment of such exploits, raising concerns about the pace of future threats.
Broader Trends in Supply-Chain Security and Public Research
The May 2026 TanStack incident is part of a broader wave of supply-chain compromises affecting over 160 packages in the ongoing Mini Shai-Hulud campaign, which includes notable targets like Mistral AI and UiPath. The attack leverages three specific vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—that had been individually documented in security research over the past 12 months. The incident underscores the persistent gap between public research disclosures and the deployment of effective mitigations, especially as AI-enhanced attack methods become more prevalent.
“The most consequential supply-chain incidents in 2026 are no longer technically novel; they are sophisticated compositions of public research executed faster than defenders can adapt.”
— Thorsten Meyer
Unresolved Aspects of the Attack Chain and Defense Gaps
While the forensic analysis confirms the chain of vulnerabilities used, it remains unclear how widespread the exploitation is beyond the TanStack incident, and whether similar chains are being actively weaponized in other campaigns. The effectiveness of current mitigations against such chained exploits is also still under assessment, and the potential for AI to automate the assembly of such attack chains is an area of ongoing investigation.
Next Steps in Mitigating Public Research-Driven Attacks
Security teams are expected to accelerate the deployment of mitigations addressing these known vulnerabilities, including stricter code review processes, improved CI/CD security measures, and proactive monitoring for suspicious activity. Additionally, the community may push for faster disclosure-to-mitigation cycles for publicly documented vulnerabilities, especially as AI tools continue to lower the barrier for assembling complex attack chains. Ongoing forensic analysis will determine if similar chains are being exploited elsewhere.
Key Questions
How did the attacker exploit publicly documented vulnerabilities so quickly?
The attacker combined three known vulnerabilities—pull request abuse, cache poisoning, and OIDC token extraction—each documented in security research over the past year, into a chain that allowed rapid exfiltration of credentials without stealing tokens or directly compromising the publish process.
What does this incident reveal about the state of software supply-chain security?
It highlights that publicly available research can be weaponized almost immediately, and current defenses may lag behind attacker tradecraft, especially when AI accelerates the assembly and deployment of complex exploits.
Are there specific mitigations that could have prevented this attack?
Implementing stricter code review policies, reducing reliance on trust boundaries, and enhancing runtime protections against token exfiltration could mitigate similar chains. However, the attack demonstrates the difficulty of blocking all potential chains once vulnerabilities are publicly known.
Is this type of attack likely to happen again?
Yes, especially as AI tools make it easier to assemble known vulnerabilities into effective chains rapidly. Continuous update and rapid deployment of mitigations are essential to counteract this trend.
Source: ThorstenMeyerAI.com
