📊 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 involved sophisticated use of GitHub Actions and trust boundary breaches, 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 the TanStack npm packages, using sophisticated techniques involving GitHub Actions and trust boundary breaches. This incident underscores how publicly available security research can be rapidly weaponized, outpacing defenders’ mitigation efforts.
The attack involved the creation of a malicious fork of the TanStack/router repository by a threat actor, who then inserted a payload via a crafted commit on May 10. The attacker used a forged author identity to evade detection. On May 11, the attacker opened a pull request that triggered GitHub Actions workflows configured with pull_request_target, which allowed the malicious code to execute with elevated permissions. The attacker then minted an OIDC token in memory, exfiltrating credentials through an encrypted messaging network, without stealing npm tokens or compromising the publish workflow itself.
The chain of vulnerabilities exploited includes three publicly documented research findings: the pull_request_target ‚Pwn Request‘ pattern, cache poisoning across trust boundaries in GitHub Actions, and OIDC token extraction from runner memory. Each vulnerability alone was insufficient, but together they enabled a fully operational supply-chain attack. The incident took place within a 28-hour window from fork creation to detection, illustrating the rapidity of modern attack tradecraft.
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
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.
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 products
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.code integrity verification software
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.
Operational Impact of the Chained Vulnerabilities
This incident demonstrates that the most significant supply-chain compromises in 2026 are not due to novel vulnerabilities but are instead sophisticated combinations of existing, publicly documented flaws. The attack highlights the difficulty for defenders to keep pace with the rapid weaponization of research, especially in open-source ecosystems like npm. It also underscores the importance of re-evaluating trust boundaries and mitigations in CI/CD pipelines to prevent similar breaches.
Broader Supply-Chain Risks and Past Incidents
The May 2026 TanStack attack is part of a wider wave of supply-chain compromises, including over 160 packages affected in the ongoing Mini Shai-Hulud campaign. The attack leverages publicly available research published over the previous 12 months, including GitHub Security Lab’s ‚Pwn Request‘ pattern (2021), cache poisoning techniques (2024), and OIDC token extraction methods (2025). These findings have been known for years but were weaponized in this incident within a short window, illustrating the challenge of timely mitigation.
This attack follows a pattern of advanced supply-chain exploits that exploit trust boundaries within CI/CD workflows, emphasizing the need for improved security controls and detection mechanisms in open-source project management.
„The TanStack incident exemplifies how public research can be rapidly weaponized, creating an attack surface that is difficult to defend against in real time.“
— Thorsten Meyer, security researcher
Unresolved Aspects of the Attack Chain
While the technical chain has been reconstructed based on forensic analysis, some details remain unclear, including the full extent of exfiltrated data, whether other repositories were targeted, and the precise timeline of attacker actions beyond the publicly disclosed steps. The full scope of compromised systems and whether additional payloads were deployed is still under investigation.
Future Security Measures and Response Strategies
Security teams are expected to review and strengthen CI/CD security controls, including stricter access policies and improved detection of malicious forks and commits. Open-source maintainers are advised to re-evaluate trust boundaries within workflows and monitor for anomalous activity. Ongoing investigations aim to determine if additional packages or projects were affected, and industry-wide, there will be increased focus on the rapid weaponization of publicly documented vulnerabilities.
Key Questions
How did the attacker bypass security measures in the TanStack pipeline?
The attacker exploited the pull_request_target pattern in GitHub Actions, which allows code from forks to run with elevated permissions, combined with previously documented vulnerabilities in cache poisoning and OIDC token extraction to exfiltrate credentials without stealing tokens or compromising the publish workflow directly.
Are all the vulnerabilities exploited in this attack publicly known?
Yes, all three vulnerabilities exploited are based on publicly documented research published between March 2024 and March 2025, making this a case of research-to-tradecraft compression.
What can open-source projects do to prevent similar attacks?
Projects should implement stricter access controls, monitor for suspicious activity, and consider limiting the use of pull_request_target workflows or sandboxing code execution. Regular security reviews of trust boundaries in CI/CD pipelines are also recommended.
Is this incident an isolated case or part of a larger trend?
This attack is part of a broader wave of supply-chain compromises affecting numerous packages, exploiting publicly available research to conduct sophisticated, rapid attacks that outpace traditional defenses.
Source: ThorstenMeyerAI.com
