GitHub Data Breach History

This page tracks the GitHub data breach history and cybersecurity incidents affecting GitHub (United States). BreachHistory currently indexes 4 publicly disclosed or catalogued incidents spanning 2013 through 2026, with approximately 500 records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.

The GitHub breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed, while 1 remain unverified claims pending independent verification.

Largest GitHub Data Breaches

The largest indexed incidents include the 2026 GitHub — South Korea police confirm 500+ PAT leak; 54 countries (Jul). Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by GitHub or a regulator. Below is the list of large data breaches:

• 2026 2026 GitHub — South Korea police confirm 500+ PAT leak; 54 countries (Jul) — about 500 records exposed · Catalogued incident

What Information Was Exposed?

Depending on the incident, exposed data may include email addresses, passwords and login credentials, names, physical addresses, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.

GitHub Data Breach 2026

At the time of this update, BreachHistory catalogues 2 2026 incidents related to GitHub. Most recent entry: 2026 GitHub — unauthorized access to internal repositories via poisoned VS Code extension (May 20). New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.

What To Do If You Were Affected

If you believe your account may have been involved in a GitHub data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.

This GitHub breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.