GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension: What Was Exposed & What To Do
The GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension (reported May 20, 2026) exposed source-code and internal-repositories belonging to roughly unknown people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.
What was exposed
- source-code
- internal-repositories
How to check if you were affected
Run a free exposure scan with your email address. It matches you against known breach datasets and shows where your information has surfaced. Check if you’re exposed →
What to do if you were in the GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension
- Remove your personal information from data-broker sites so the leaked data can’t be combined against you — GalaxyWarden files those removals for you.
How this breach connects
Frequently asked questions
Was my data in the GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension breach?
The fastest way to know is a free exposure scan — it checks your email address against known breach data, including recent incidents like this one.
What information was exposed in the GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension?
The reported exposed data includes: source-code, internal-repositories.
What should I do after the GitHub Confirms Breach of ~3,800 Internal Repos via Malicious VS Code Extension breach?
Change your password for that account and anywhere you reused it, turn on two-factor authentication, and remove your personal information from data-broker sites so it can’t be combined with the leaked data.
More recent breaches
Accenture confirms 35GB source code and cloud keys breachAccenture confirms breach after 35GB source code offered for saleBrazilian IT Firm Service IT Breached by WorldLeaksNissan Discloses Employee Data Breach via Oracle PeopleSoft Zero-DayAttributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.