CrowdSec Says TanStack npm Attack Led to Copy of 170 Private GitHub Repositories
CrowdSec private GitHub repos copied after former employee's laptop compromised via npm attack.
An attacker gained access to approximately 170 of CrowdSec's private GitHub repositories by exploiting a former employee's compromised laptop. The compromise stemmed from a supply chain attack on TanStack's npm packages, which stole credentials, including GitHub tokens. The stolen code, which also contained user and investor data, was posted online. CrowdSec stated that its core infrastructure and databases were not accessed, and no code was altered.
AI summary of the linked source. Not reviewed by an editor. How this works
Run TanStack?
Get an email when a new story names TanStack, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA malicious supply chain attack targeting TanStack's npm packages allowed an attacker to steal GitHub tokens from a former employee's laptop, granting unauthorized access to approximately 170 of CrowdSec's private repositories. The core failure was twofold: a compromised third-party dependency silently harvested credentials, and offboarding processes failed to revoke the former employee's access tokens before the breach occurred. Stolen data included source code, user information, and investor data — demonstrating that supply chain compromises can cascade far beyond their initial entry point. This incident highlights how a single unrotated credential from a departed employee can expose an entire organization's codebase.
What helps against this
How we list vendors- Identity governance and single sign-on
People who leave or change roles lose access everywhere at once, and forgotten accounts stop piling up.
- Secrets management
API keys, tokens and passwords stop leaking from code, chat and configuration files.
- Device management (MDM and UEM)
Every company laptop and phone is known, encrypted, locked down and up to date.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- cve — CVE-2026-45321