TanStack npm Supply Chain Hit Copies 170 CrowdSec Private Repos via Stolen GitHub Token

On May 11, 84 malicious versions of 42 TanStack packages were uploaded under CVE-2026-45321. Execution on developer machines harvested GitHub tokens, SSH keys, and cloud credentials. Eleven days later the token from a recently departed CrowdSec engineer was used to clone private repositories before access was revoked on May 25. No infrastructure changes or database access occurred.

CrowdSec's September 18 disclosure lists the leaked contents as its web console, data science models, automation scripts, and the IP blocklist consensus algorithm with its detection thresholds. The same token theft also touched Mistral AI and OpenAI devices, confirming a multi-target credential harvest rather than an isolated incident. GitHub token logs left no trace; only later support tracing confirmed the TanStack vector.

The incident reveals persistent offboarding gaps across security firms: retained tokens for transitional work created a single point of failure that bypassed AWS monitoring. Leaked consensus thresholds and investor details from 2020 remain low-value for poisoning the shared blocklist, yet they expose operational parameters previously withheld from the 150,000-user community.

CrowdSec has rotated remaining credentials and will notify affected users and investors. Similar token-harvesting campaigns against other npm ecosystems are expected within the next quarter as attackers replicate the low-cost credential exfiltration pattern.