Crypt0gnome avatar

Security Alert for All HIVE Devs & Vibecoders: TanStack npm Supply-Chain Compromise

crypt0gnome

Published: 12 May 2026 › Updated: 12 May 2026Security Alert for All HIVE Devs & Vibecoders: TanStack npm Supply-Chain Compromise

Security Alert for All HIVE Devs & Vibecoders: TanStack npm Supply-Chain Compromise

image.png

Hey fellow HIVE builders, vibecoders, and JS/TS developers!

If you maintain any frontend, full-stack, or CLI projects that depend on tanstack@tanstack/ packages (Router, Query, Table, etc.), stop and read this right now.

What Happened

On May 11, 2026 between 19:20–19:30 UTC, an attacker published 84 malicious versions across 42 tanstack@tanstack/ packages.

The malicious versions were live for only a few hours before being deprecated. Anyone who ran npm install, pnpm install, yarn install, or resolved @latest in that window is potentially compromised.

Severity: HIGH

The payload exfiltrates:

  • AWS, GCP, Kubernetes & Vault credentials
  • GitHub tokens
  • ~/.npmrc contents
  • SSH keys

It also installs persistence and tries to spread further.

How to Detect If You're Affected

Search your node_modules for this suspicious entry in any package.json:

"optionalDependencies": {
  "@tanstack/setup": "github:tanstack/router#79ac49ee..."
}

Or look for a large router_init.js (~2.3 MB) file. If found → treat the machine as compromised.

Immediate Actions

  1. Rotate all credentials immediately (cloud keys, GitHub tokens, SSH keys, npm tokens)
  2. Audit your cloud provider logs for the last 24 hours
  3. Pin to a known-good version and reinstall from a clean lockfile
  4. Full details + complete list: https://github.com/TanStack/router/issues/7383

Best Protection Going Forward

  1. Switch to pnpm (best supply-chain protections)
  2. Set minimum release age — this alone would have blocked the attack.

Add to your project .npmrc (and ideally ~/.npmrc globally):

# pnpm
minimum-release-age=10080   # 7 days (1440 = 24h)

# npm
min-release-age=7d

Recommended hardened .npmrc:

ignore-scripts=true
minimum-release-age=10080
strict-peer-dependencies=true

Why This Matters on HIVE

We build fast and often use latest packages. One bad install in CI/CD can leak keys.

Let's raise the bar:

  • Always use lockfiles
  • Pin your deps
  • Enable minimum-release-age by default
  • Review GitHub Actions carefully

Stay safe and keep shipping! Drop a comment if you want a ready-to-use .npmrc template or scan script.

Leave Security Alert for All HIVE Devs & Vibecoders: TanStack npm Supply-Chain Compromise to:

Written by

Building @Terracore & @hive-swap.com on #HIVE

Read more #devs posts


Best Posts From Crypt0gnome

We have not curated any of crypt0gnome's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.

More Posts From Crypt0gnome