Skip to content
Start with Identity
Identity breach database · 2026 · OAuth token abuse

CrowdSec private repositories copied with a departing engineer's GitHub token

CrowdSec said on September 17, 2026 that source code had been exposed, first linking it to the May 11 TanStack npm attack. Its September 18 report instead traced the copy to a former employee's GitHub account, left open so he could finish some work, whose still-valid OAuth token was used on May 22 to copy about 170 private repositories. The account was removed from the organization on May 25 and the code appeared on a forum in September; the two statements disagree on whether user and investor data leaked.

Victim
CrowdSec
Industry
Technology
Country
France
Intrusion began
May 22, 2026
First disclosed
Sep 17, 2026
Actor
Unattributed
Initial access
OAuth token abuse
Identity control that failed
Identity lifecycle
MFA
Not applicable (no interactive login)
Abused identity
Human account
Records affected
Not disclosed
Disclosed cost
Not disclosed

The identity lesson

Access kept open for a leaver, through a token that bypasses MFA, did the damage. Offboarding should revoke OAuth tokens and organization membership on the last day, with exceptions time-boxed and monitored.

Go deeper on SWI

Sources

  1. CrowdSec Statement: Source Code Exposure in May 2026, CrowdSec, Sep 17, 2026
  2. TanStack Supply Chain Attack Analysis, CrowdSec, Sep 18, 2026
  3. CrowdSec Says TanStack npm Attack Led to Copy of 170 Private GitHub Repositories, The Hacker News, Sep 19, 2026

Record verified Oct 31, 2026 against the sources above. Corrections: contact us.

Related incidents

Cite this record

SWI Community Team. (2026). CrowdSec private repositories copied with a departing engineer's GitHub token. Identity Breach Database, Start with Identity. https://startwithidentity.com/breaches/incidents/2026-crowdsec-departing-engineer-github-token/

Part of the Identity Breach Database, free to reuse under CC BY 4.0. Analysis across every record: Identity Breach Report 2026.