📊 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 within six minutes. This incident highlights how publicly known security flaws can be weaponized rapidly, outpacing defenses.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise TanStack npm packages within six minutes, using AI-augmented tradecraft that outpaced defenders’ mitigation efforts. The incident involved the malicious publishing of 84 packages across 42 npm modules, despite the maintainers’ security measures. This event underscores how publicly available research can be weaponized rapidly in 2026’s supply chain cyberattacks, making it a critical concern for open-source and enterprise security.
The attack was executed by creating a malicious fork of the TanStack/router repository, then submitting a pull request that triggered the compromised CI/CD workflows via GitHub Actions. The attacker, identified as user zblgg, used a fabricated author identity to inject a large JavaScript payload. Using previously documented vulnerabilities—such as the pull_request_target ‘Pwn Request’ pattern, cache poisoning across trust boundaries, and OIDC token extraction from GitHub Actions runner memory—the attacker minted an in-memory OIDC token and exfiltrated credentials through the encrypted Session Protocol network. The chain of vulnerabilities, each publicly documented over the previous year, was necessary but not sufficient alone; their combination enabled the attack. The incident was detected 28 hours after initial fork creation, with the attacker deploying malicious packages within six minutes of the first commit.
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
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.
CI/CD Pipeline Using Jenkins Unleashed: Solutions While Setting Up CI/CD Processes
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 Exploitation in Supply Chain Attacks
This incident exemplifies how publicly available security research can be rapidly weaponized, creating a significant challenge for defenders. The attack demonstrates that the most consequential supply chain breaches in 2026 are not due to new or unknown vulnerabilities but are composed of well-understood flaws exploited in quick succession. It highlights the need for faster deployment of mitigations and the importance of holistic security practices that consider the entire attack chain, especially in open-source ecosystems where trust boundaries are complex and often exploited.
Publicly Documented Vulnerabilities and the 2026 Supply Chain Wave
Over the past year, researchers documented three key vulnerabilities that, when chained, enable sophisticated supply chain attacks. These include the ‘Pwn Request’ pattern (GitHub Security Lab, 2021), cache poisoning across trust boundaries (Adnan Khan, May 2024), and OIDC token extraction from GitHub Actions runners (StepSecurity, March 2025). Despite being publicly known, these flaws were not collectively mitigated, allowing attackers to combine them in a single campaign. The May 11 incident is part of a broader wave of supply chain compromises affecting over 160 packages, including major AI and enterprise tools, illustrating the scale and sophistication of the ongoing threat landscape.
“The TanStack attack demonstrates that in 2026, the most damaging supply chain breaches are less about new vulnerabilities and more about the rapid, weaponized combination of existing research.”
— Thorsten Meyer, security researcher
Unresolved Aspects of the Attack Chain and Mitigations
Details remain unclear regarding the full extent of the exfiltrated data, the precise scope of affected packages beyond those identified, and whether additional vulnerabilities or attack vectors were involved. The speed at which defenders can deploy mitigations against such chained vulnerabilities is also still under assessment, as is the effectiveness of current security controls in preventing similar future incidents.
Next Steps for Detection, Mitigation, and Prevention
Security teams are expected to analyze the attack chain in detail, update best practices for CI/CD security, and accelerate the deployment of mitigations for publicly documented vulnerabilities. The incident will likely prompt revisions to open-source and enterprise security policies, as well as increased scrutiny of trust boundaries in automation workflows. Ongoing forensic investigations aim to quantify the full impact and develop more resilient defense strategies against chained, publicly known vulnerabilities.
Key Questions
How did the attacker bypass security measures despite the use of 2FA and trusted publishing?
The attacker exploited a chain of three publicly documented vulnerabilities that, when combined, allowed them to forge tokens, inject malicious code, and exfiltrate credentials without stealing npm tokens or compromising the publish workflow directly.
Are similar attacks likely to happen again using publicly known vulnerabilities?
Yes, especially if defenders do not accelerate mitigation deployment or address the entire attack chain. The incident demonstrates that well-understood vulnerabilities can be weaponized rapidly in combination.
What can open-source maintainers do to prevent such attacks?
Implement comprehensive security reviews of CI/CD workflows, monitor for suspicious activity in forks, and apply faster patching or mitigation strategies for publicly documented vulnerabilities.
Will this incident lead to new security standards or regulations?
It is possible that this will accelerate discussions around stricter security practices in open-source ecosystems and supply chain security regulations, emphasizing faster response to known vulnerabilities.
Source: ThorstenMeyerAI.com
