CVE-2026-45321: @tanstack arktype-adapter · Embedded Malicious Code
Affects @tanstack arktype-adapterSource CVE Database V5
Exploited in the wild · used in ransomware campaigns · KEV due 10 Jun 2026 · 3% EPSS : apply the vendor's fix or mitigations to @tanstack arktype-adapter now.
Data as of 30 Oct 2026, 11:52 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
- Ransomware
- Used in ransomware campaigns
- EPSS
- 3.2% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 15 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 3 hours before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 2 hours after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
, 15 days after disclosure
KEV remediation due
US federal deadline
, 29 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @tanstackarktype-adapter | Affected
| Fixed in– |
| @tanstackeslint-plugin-router | Affected
| Fixed in– |
| @tanstackeslint-plugin-start | Affected
| Fixed in– |
| @tanstackhistory | Affected
| Fixed in– |
| @tanstacknitro-v2-vite-plugin | Affected
| Fixed in– |
| @tanstackreact-router | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
References
- github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx (opens in a new tab)
- github.com/TanStack/router/issues/7383 (opens in a new tab)
- tanstack.com/blog/npm-supply-chain-compromise-postmortem (opens in a new tab)
- stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem (opens in a new tab)
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-45321 (opens in a new tab)