📊 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 in TanStack npm packages, leading to a widespread supply chain attack. The attack leveraged known weaknesses in GitHub Actions and trust boundaries, executed faster than defenses could respond.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages, leading to a widespread supply chain attack. The incident involved the creation of malicious package versions via GitHub Actions workflows, without theft of npm tokens, but through in-memory exfiltration of credentials. This event exemplifies how publicly known security flaws can be weaponized rapidly in a coordinated attack.
The attack was carried out by creating a malicious fork of the TanStack/router repository on GitHub, then submitting a pull request that triggered the compromised workflow. The attacker used a forged author identity, added a large JavaScript payload, and injected malicious code into the release process. The attack leveraged three vulnerabilities: the pull_request_target ‘pwn request’ pattern, cache poisoning across trust boundaries, and in-memory OIDC token extraction from GitHub Actions runners. All three vulnerabilities had been publicly documented prior to the attack, with timelines indicating at least 12 months between the last research publication and the incident.
Despite the use of multi-factor authentication and OIDC trusted publisher bindings, the chain of vulnerabilities allowed the attacker to exfiltrate credentials without stealing npm tokens or compromising the publish workflow directly. The attack was detected within 28 hours, and forensic analysis traced the chain of exploits from initial fork creation to malicious package release.
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
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.
ID Scanner for Bars and Clubs – Easy to Use and Reliable ID Checker for Your Business that Detects Expired IDs & Underage Customers – Works in All 50 States – Includes Optional Fake ID Detection
Unlimited Standard ID Scanning — Always Free – Instantly verifies age and expiration on every scan and automatically…
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.
Automating DevOps with GitLab CI/CD Pipelines: Build efficient CI/CD pipelines to verify, secure, and deploy your code using real-life examples
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 publicly available security research can be weaponized in sophisticated attacks, often outpacing defenders’ ability to deploy mitigations. The attack’s reliance on known vulnerabilities highlights the importance of re-evaluating trust boundaries and implementing layered defenses in software supply chains. It underscores the need for rapid patching, better detection of suspicious activity, and more robust security practices for open-source projects and enterprise integrations.
Publicly Documented Vulnerabilities Facilitating the Attack
Over the past year, three key vulnerabilities relevant to this attack were published in security research: the pull_request_target ‘Pwn Request’ pattern (GitHub Security Lab, 2021), cache poisoning across fork and base trust boundaries (Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runners (StepSecurity, March 2025). Each vulnerability independently posed a risk, but their combined exploitation in this chain was unprecedented. The attack occurred within a broader wave of supply chain compromises in 2026, affecting over 160 packages in the ecosystem, part of the ongoing Mini Shai-Hulud campaign.
“The attack demonstrates how publicly available research can be rapidly weaponized, surpassing defenders’ deployment speed.”
— Thorsten Meyer
Remaining Questions About Attack Scope and Mitigations
It is not yet clear how many packages or projects were affected beyond TanStack, or whether additional undetected malicious versions exist. The full extent of compromised systems and the effectiveness of mitigations deployed post-attack are still being assessed. Details about attacker identity and whether similar chains are being exploited elsewhere remain under investigation.
Future Steps for Detection and Prevention of Chain Exploits
Security teams are expected to enhance monitoring for similar chain exploits, improve detection of malicious forks, and review trust boundaries in CI/CD pipelines. The incident underscores the need for faster deployment of mitigations based on publicly available research. Further analysis will focus on identifying other potential chains of known vulnerabilities and strengthening defenses across the software supply chain.
Key Questions
How did the attacker exploit the vulnerabilities without stealing npm tokens?
The attacker minted an OIDC token in memory during the workflow execution and exfiltrated credentials via the encrypted Session Protocol, avoiding the need to steal npm tokens or directly compromise the publish process.
Are other packages or projects at similar risk from publicly documented vulnerabilities?
Yes, any project using GitHub Actions with similar trust boundaries and configurations may be vulnerable if they have not implemented additional safeguards against known attack patterns.
What measures can prevent similar attacks in the future?
Implementing stricter code review processes, limiting trust boundaries, monitoring for suspicious activity, and applying rapid patching based on public research can reduce risk.
While both events occurred on May 11, 2026, and involve AI-augmented offensive techniques, they are separate incidents. The zero-day involved AI-generated exploits, whereas this attack used publicly known vulnerabilities in a chain.
Source: ThorstenMeyerAI.com
