basicsecurity.net
Proof, not just disclosure.
Threats / TanStack / CVE-2026-45321
CVE-2026-45321 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-06

TanStack vulnerability

TanStack vulnerability allowed malicious versions to be published to npm registry, distributing credential-stealing malware under a trusted identity.

Verdict

Today item, not a backlog item.

An unspecified vulnerability in TanStack's supply chain enabled attackers to publish compromised packages to npm, delivering credential theft malware to developers who installed the trojanized versions.

CISA KEV Yes · 2026-05-273Ransomware use Flagged3EPSS 0.17051 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-27), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.17051 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: TanStack, TanStack. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I exploit a weakness in TanStack's publishing or authentication controls to gain unauthorized access to publish packages.
Business
Developers unknowingly install malicious TanStack versions, exposing credentials and enabling lateral movement into customer environments.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I publish credential-stealing malware under TanStack's trusted identity on npm, leveraging the brand's reputation to avoid detection.
Business
Supply chain compromise affects all downstream users of TanStack, creating widespread exposure across the JavaScript ecosystem.
3

Lateral reach — past segmentation narrative 3

Attacker
I harvest stolen credentials from infected developer machines and systems running the trojanized package.
Business
Attackers gain access to sensitive systems, intellectual property, and infrastructure, enabling ransomware deployment and data exfiltration.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Catalogued by GitHub_M (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by GitHub_MCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.