📊 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 used known flaws in GitHub Actions and trust boundaries, 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, using known flaws in GitHub Actions workflows and trust boundaries. This incident demonstrates how publicly available security research can be utilized in real-world attack scenarios, with potential implications for security practices. The attack involved publishing malicious package versions via an OIDC token exfiltration, with no tokens stolen or workflows compromised directly.
The attack was orchestrated through a series of chained vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across fork and base repositories, and extraction of OIDC tokens from GitHub Actions runner memory. These vulnerabilities, each documented in public security research before 2026, were exploited within a six-minute window to publish 84 malicious versions of @tanstack/* packages. The attacker created a fork of TanStack/router, inserted malicious code, and triggered the release workflow using a trusted-publisher binding via GitHub Actions.
The attacker exfiltrated credentials by minting an in-memory OIDC token and transmitting it through the Session Protocol, an encrypted messaging network, without stealing npm tokens or directly compromising the publish workflow. The chain of vulnerabilities bridged trust boundaries: from fork code crossing into cache, into the runtime environment, and finally enabling write access to the npm registry. All three vulnerabilities had been individually documented in security research between March 2025 and May 2024, but their combined exploitation was unprecedented.
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.
Network Vulnerability Assessment: Identify security loopholes in your network's infrastructure
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 audit tools
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 Analyst Call Humor Soc Cybersecurity T-Shirt
For the infosec professional who lives by zero trust, ethical hacking and incident response at 3am. Always On…
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 Exploited in Supply Chain Attack
This incident demonstrates that publicly available security research can be leveraged in attack scenarios, which may lead to complex vulnerabilities in software supply chains. It highlights the importance of ongoing security reviews and layered defenses within open-source ecosystems, where trust boundaries are critical points. The reliance on known vulnerabilities underscores the need for continuous security monitoring and mitigation strategies.
Pre-existing Public Vulnerabilities Enabling the Attack
Three vulnerabilities were central to the attack, each publicly documented before 2026: the pull_request_target pattern (GitHub Security Lab, 2019), cache poisoning across fork boundaries (Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runners (StepSecurity, March 2025). These findings described methods for crossing trust boundaries in CI/CD workflows, manipulating cache, and exfiltrating credentials, but had not been combined into a practical attack until May 2026. The incident reflects a broader trend where attacker techniques are accelerated by recombining existing research.
“The TanStack attack illustrates how publicly available security research can be utilized in attack scenarios, emphasizing the importance of ongoing security assessments.”
— Thorsten Meyer, security researcher
Unresolved Aspects of the Attack Chain and Mitigations
While the technical chain has been reconstructed and publicly documented, details remain unclear regarding the attacker’s full operational capabilities, whether additional vulnerabilities were exploited, and the extent of data impacted. It is also uncertain how quickly mitigation strategies can be implemented to prevent similar future attacks, given the rapid application of publicly available research.
Future Security Measures and Response Strategies
Security teams and open-source maintainers are advised to review and strengthen trust boundaries within CI/CD pipelines, implement thorough code review processes, and develop detection mechanisms for chained vulnerabilities. Continued analysis will help identify if additional vulnerabilities are being exploited and evaluate the effectiveness of mitigation strategies. The incident emphasizes the importance of proactive security practices and ongoing monitoring.
Key Questions
How did the attacker exploit the vulnerabilities?
The attacker created a malicious fork, inserted payloads exploiting known trust boundary vulnerabilities, and used GitHub Actions workflows to publish malicious package versions without stealing tokens or directly compromising workflows.
Are these vulnerabilities still exploitable?
The vulnerabilities are publicly known, but their current exploitability depends on whether appropriate mitigations have been applied. Users are advised to update affected workflows and repositories accordingly.
What can open-source maintainers do to prevent similar attacks?
Maintain strict code review procedures, monitor for suspicious activity in forks, limit trust boundaries where possible, and consider implementing real-time detection for chained vulnerabilities to reduce attack surface.
Does this incident suggest a broader trend?
Yes, it demonstrates how publicly documented vulnerabilities can be combined into more complex attack chains, underscoring the importance of proactive security measures in software supply chains.
Source: ThorstenMeyerAI.com
