The tweet was deleted by the author.
But we saved everything 🙂.
GitHub, the Microsoft-owned platform, has confirmed that attackers gained unauthorized access to its internal repositories by compromising an employee’s device through a malicious Visual Studio Code extension. The company detected the breach, isolated the affected endpoint, removed the harmful extension, and immediately launched an incident response.
According to CoinPedia, GitHub stated that the number of affected internal repositories—approximately 3,800—aligns with the attacker’s claims. The cybercriminal group TeamPCP has claimed responsibility and is reportedly attempting to sell the stolen data on underground forums for more than $50,000. The leaked materials reportedly include proprietary source code and internal organizational files.
Importantly, GitHub emphasized that the breach was limited to its internal systems. Customer repositories, enterprise organizations, and user data stored outside internal GitHub systems were not affected.
GitHub acted quickly after discovery: it isolated the compromised device, revoked and rotated critical credentials (prioritizing the most sensitive ones), and continues to monitor for any secondary activity. The company said it will publish a more detailed report once the investigation is complete and will notify customers through official channels if any customer data is found to be impacted.
Security experts recommend that all developers review and rotate API keys and credentials stored in their repositories as a precautionary measure, even if their repositories were not directly affected.
GitHub has rotated critical secrets and is actively monitoring for further activity.
This incident serves as a stark reminder of how vulnerable even the largest technology platforms can be. An attack delivered through a seemingly routine developer tool—a VS Code extension—highlights the growing threat to the software supply chain.
For millions of developers worldwide, it underscores the need for greater vigilance: regularly auditing installed extensions, practicing strict credential hygiene, and maintaining strong security awareness. While GitHub responded swiftly, the full implications of the breach may take time to become clear as the investigation continues.
Earlier, we reported that hackers used GitHub for crypto crimes.