📊 Full opportunity report: Three Public Vulnerabilities. Chained. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
In May 2026, attackers exploited a chain of three publicly known vulnerabilities to compromise TanStack npm packages within six minutes. This incident underscores how public research can be weaponized faster than defenses can adapt.
On May 11, 2026, attackers exploited a chain of three publicly documented vulnerabilities to compromise the TanStack npm packages within six minutes, using a sophisticated attack that bypassed multiple security controls. This incident highlights how publicly available research can be weaponized rapidly, posing a significant threat to open-source supply chains and enterprise software security.
The attack involved creating a malicious fork of the TanStack/router repository, deploying a crafted commit, and executing a pull request that triggered malicious workflows. The attacker, using a forged identity, uploaded a large payload via an attacker-controlled fork, then exploited a vulnerability in GitHub Actions’ pull_request_target pattern, which allows code from forks to run with elevated permissions.
Three vulnerabilities, each documented in public security research before 2026, were chained to enable the attack: the pull_request_target “Pwn Request” pattern (GitHub Security Lab, 2019), cache poisoning across fork and base trust boundaries (Adnan Khan, 2024), and OIDC token extraction from GitHub Actions runner memory (StepSecurity, 2025). Each was necessary for the attack; none alone would suffice. The attacker minted an OIDC token in memory, exfiltrating credentials via an encrypted messaging network without control over command-and-control infrastructure.
Despite the TanStack team’s security measures, including 2FA and OIDC trusted publishing, the chain of vulnerabilities allowed the attacker to bypass safeguards and publish malicious package versions. The attack was detected 28 hours after initial compromise, during which the attacker maintained persistence through multiple commits and pull requests.
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.
The ICS Cybersecurity Field Manual: VOL. 1-3 Plus EXCLUSIVE BONUS material
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
Open Source Security Tools: Practical Applications for Security (Bruce Perens' Open Source)
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.npm package security audit tools
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.
Essential Home Security: A Layman's Guide
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 the Chained Vulnerabilities in Supply Chain Security
This incident demonstrates that the most impactful supply-chain compromises in 2026 are not due to zero-day exploits but are instead the result of chaining publicly known vulnerabilities. It underscores how attacker tradecraft rapidly incorporates published research, outpacing defenses. The attack highlights the need for more robust safeguards against the combination of multiple vulnerabilities, especially those documented in public research, which can be exploited in sequence to breach even security-conscious organizations.
Broader Trends in 2026 Supply-Chain Attacks and Public Research Exploitation
The May 2026 TanStack incident is part of a wave of supply-chain attacks exploiting publicly documented vulnerabilities. Over the past year, researchers identified three key weaknesses: the pull_request_target pattern (2019), cache poisoning across trust boundaries (2024), and OIDC token extraction (2025). These vulnerabilities, once known, became tools in the hands of attackers to execute complex, multi-stage compromises.
The incident is also linked to the broader Mini Shai-Hulud campaign, which has compromised over 160 packages across various ecosystems, including Mistral AI, UiPath, and Squawk. The attack timeline indicates a rapid development cycle, with attacker activity beginning as early as May 10, 2026, and culminating in the package compromise on May 11, within minutes of the malicious fork creation.
“This attack exemplifies how public research, once published, becomes attacker tradecraft that can be weaponized faster than defenders can deploy mitigations.”
— Thorsten Meyer, security researcher
Remaining Questions About Attack Scope and Mitigations
It is not yet clear how widespread the impact is beyond the TanStack packages or whether other ecosystems have been similarly targeted using this chained vulnerability approach. The full extent of compromised systems and the attacker’s operational capabilities remain under investigation. Additionally, the effectiveness of current mitigations and how quickly organizations can adapt to such multi-vulnerability chains are still being assessed.
Next Steps for Detection, Response, and Prevention
Security teams are expected to review and tighten controls around pull request workflows, especially the use of pull_request_target, and improve monitoring for suspicious activity in CI/CD pipelines. Developers and maintainers should audit their dependencies and trust boundaries, applying patches and mitigations for publicly documented vulnerabilities. Ongoing forensic analysis aims to determine the full scope of the breach and develop strategies to prevent similar chained attacks in the future.
Key Questions
How did the attacker exploit publicly documented vulnerabilities?
The attacker chained three known vulnerabilities—trust boundary exploitation via pull_request_target, cache poisoning, and OIDC token extraction—to bypass security controls and publish malicious package versions within minutes.
What makes this attack different from previous supply chain incidents?
This attack used publicly available research to craft a sophisticated chain of vulnerabilities, demonstrating that the most impactful 2026 supply chain incidents are based on well-documented flaws exploited in sequence, not zero-days.
Are current security controls sufficient to prevent similar attacks?
Current controls may be insufficient against chained vulnerabilities that leverage public research. Organizations need to review trust boundaries, pipeline configurations, and dependency management to mitigate such risks.
What should open-source maintainers do to protect their projects?
Maintain strict review processes for pull requests, limit trusted workflows, monitor for suspicious activity, and stay informed about public research that could be weaponized in attacks.
Source: ThorstenMeyerAI.com
