📊 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 published research to bypass defenses, highlighting the speed of offensive tradecraft outpacing mitigation efforts.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages, using known research to bypass security defenses. The attack involved publishing malicious package versions via GitHub Actions workflows, without stealing tokens or compromising the publish process itself. This incident exemplifies how publicly available research can be weaponized rapidly in supply-chain attacks, outpacing defenders’ mitigation efforts.
The attack was executed on May 11, 2026, by publishing 84 malicious package versions across 42 TanStack npm packages within six minutes. The attacker used GitHub Actions’ OIDC trusted-publisher binding to authenticate, without stealing npm tokens or compromising the publishing workflow. Instead, the attacker minted an in-memory OIDC token and exfiltrated credentials through the encrypted Session Protocol network, avoiding command-and-control infrastructure.
Forensic analysis revealed that the attack relied on a chain of three known vulnerabilities: the pull_request_target “Pwn Request” pattern, cache poisoning across fork and base trust boundaries, and OIDC token extraction from runner memory. Each vulnerability had been publicly documented prior to the attack—by GitHub Security Lab, Adnan Khan, and StepSecurity respectively—and each was necessary for the attack to succeed. None alone was sufficient, but combined, they created a pathway for malicious code execution and package compromise.
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.
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 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.
Impact of Public Research on Supply-Chain Security
This incident underscores how publicly available security research can be weaponized rapidly, enabling sophisticated supply-chain attacks that exploit known vulnerabilities. The attack demonstrates that even security-conscious teams with multi-factor authentication and trusted publishing workflows are vulnerable when multiple known flaws are chained together. It highlights the need for faster deployment of mitigations and continuous monitoring for attack patterns based on published research, especially as AI-augmented attack techniques evolve.
Pre-Existing Research and the Attack Chain
Prior to the May 11, 2026, incident, three key vulnerabilities had been publicly documented: the GitHub pull_request_target “Pwn Request” pattern (by GitHub Security Lab, 2019), 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). These findings outlined pathways for exploiting CI/CD workflows and trust boundaries in software supply chains. The attack combined these known vulnerabilities in a sequence that bridged trust boundaries, effectively weaponizing open-source research into operational tradecraft.
“The TanStack incident exemplifies how publicly documented security research can be rapidly weaponized, outpacing defensive mitigation deployment.”
— Thorsten Meyer
Unresolved Aspects of the Attack Chain
While the forensic analysis confirms the chain of vulnerabilities used, it remains unclear how quickly defenders can deploy mitigations against such rapid, research-based attacks. The precise extent of the breach’s impact on other packages or ecosystems is still being assessed, and the full scope of compromised workflows or additional vulnerabilities exploited remains unknown. Additionally, the broader prevalence of similar attack chains in other supply chains has not yet been fully determined.
Future Steps for Defense and Monitoring
Security teams are expected to enhance detection of chained vulnerabilities and implement faster mitigation strategies. Ongoing monitoring for similar attack patterns in open-source and enterprise workflows will be prioritized. The incident also underscores the importance of reviewing trust boundaries, access controls, and dependency management in CI/CD pipelines. Researchers and vendors will likely accelerate efforts to identify and patch chained vulnerabilities before they can be exploited at scale.
Key Questions
How did the attacker bypass security controls in the TanStack incident?
The attacker exploited a chain of publicly documented vulnerabilities—pull_request_target abuse, cache poisoning, and OIDC token extraction—that together created a pathway to compromise packages without stealing tokens or directly breaching the publish process.
Are these vulnerabilities still exploitable in other projects?
Yes, since each vulnerability is publicly documented and affects common CI/CD practices, other projects with similar workflows remain at risk unless mitigations are applied.
What can open-source maintainers do to prevent similar attacks?
Maintainers should review trust boundaries, avoid unsafe patterns like pull_request_target in untrusted workflows, and implement rapid detection and response mechanisms for chained vulnerabilities.
Does this incident indicate a new type of attack?
No, the attack used known vulnerabilities combined in a novel chain, illustrating how existing research can be weaponized quickly rather than introducing entirely new attack techniques.
What lessons does this incident teach for enterprise security?
Organizations must recognize that publicly available research can be rapidly turned into operational attack tradecraft, emphasizing the need for continuous review of trust boundaries and proactive mitigation of known vulnerabilities.
Source: ThorstenMeyerAI.com
