TanStack npm Attack Exposed 170 Private CrowdSec Repos
By @sharedot · · 6 pages
- Programming
- Supply Chain Security
- Github
- Npm
CrowdSec says attackers linked to the TanStack npm compromise used a former employee's GitHub OAuth token to clone roughly 170 private repositories.
What happened
CrowdSec disclosed that the May 2026 TanStack npm supply-chain compromise — in which the group TeamPCP, also tracked as UNC6780, backdoored 42 packages on May 11 with the credential-harvesting malware Shai Hulud — led to the theft of its private source code.
Between 05:52 and 06:01 UTC on May 22, an attacker used a GitHub OAuth token tied to a recently departed employee's account to clone approximately 170 repositories, a mix of more than 130 public projects and private code including the SaaS console, data-science scripts, automation tooling, and the company's Consensus Algorithm.
The attacker later published the archive on a breach forum on September 16.
Why it is surprising
The surprising twist is that a third-party npm compromise reached CrowdSec without touching CrowdSec's own infrastructure at all.
According to both Cyber Press and GBHackers News, forensic analysis found a GitHub remote URL containing an oauth2:gho_ token, confirming the cloning relied on a stolen developer credential rather than any direct breach of production systems, databases, or CI/CD pipelines.
The token belonged to a departing employee whose account CrowdSec had deliberately left in the organization to finish outstanding work — and it had already expired or been revoked before the incident was discovered, forcing the company to lean on GitHub support to reconstruct the token's lifecycle from audit records.
Git metadata tied the activity to an IP geolocated to Toronto, Canada, with a UTC-4 system timezone.
The evidence and blast radius
The newest commits in the leaked archive dated to May 22, which helped investigators establish the date and scope of the theft. CrowdSec said the attacker committed no code, modified no repositories or CI/CD workflows, and never accessed AWS infrastructure.
The leaked codebase contained one still-valid AWS SNS credential — GBHackers News identifies it as assertible-zapier-sns-sender — narrowly scoped to publishing notifications to a single topic; an unidentified actor tested it on August 17 from IP 23.234.84.102, but the IAM role's limited permissions stopped the activity at GetCallerIdentity and ListTopics checks.
The archive also exposed email addresses for 83 users, under 0.05% of roughly 150,000 users, and details on 51 potential investors from 2020.
Stakes and what comes next
The incident is a working-programmer cautionary tale: existing controls including 2FA, privilege separation, scoped cloud permissions, and secrets management limited the damage, but none of them stopped a compromised developer endpoint from yielding a valid GitHub token.
CrowdSec has since deployed endpoint detection and response on workstations that access code or infrastructure, and plans to strengthen GitHub activity monitoring, accelerate credential reviews, and reinforce offboarding procedures.
The company also credits GitHub, GitGuardian, Aikido, and Fuites Info with assisting the response, and says it will notify affected individuals and report to authorities.
For teams everywhere, the lesson is that offboarding, token lifetimes, and dependency security now matter as much as perimeter defense.