Skip to main content
VulnerabilityPublished Updated

CVE-2026-45321: @tanstack arktype-adapter · Embedded Malicious Code

Affects @tanstack arktype-adapterSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 15 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 3 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 2 hours after disclosure

  4. Added to CISA KEV (opens in a new tab)

    exploitation confirmed · ransomware use known

    , 15 days after disclosure

  5. 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

ProductAffectedFixed in
@tanstackarktype-adapterAffected
  • =1.166.12
  • =1.166.15
Fixed in–
@tanstackeslint-plugin-routerAffected
  • =1.161.9
  • =1.161.12
Fixed in–
@tanstackeslint-plugin-startAffected
  • =0.0.4
  • =0.0.7
Fixed in–
@tanstackhistoryAffected
  • =1.161.9
  • =1.161.12
Fixed in–
@tanstacknitro-v2-vite-pluginAffected
  • =1.154.12
  • =1.154.15
Fixed in–
@tanstackreact-routerAffected
  • =1.169.5
  • =1.169.8
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

Community reviews

Loading reviews…