TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
GitHub has confirmed that around 3,800 internal repositories were accessed following the installation of a trojanized VS Code extension by an employee. The breach is under investigation, with no evidence yet of customer data compromise.
GitHub has confirmed that approximately 3,800 internal repositories were accessed after an employee installed a malicious Visual Studio Code extension. The breach was detected and contained on the same day, with the company securing the compromised device and removing the malicious extension from the VS Code Marketplace. This incident highlights ongoing security risks associated with third-party extensions and internal device security.
According to GitHub, the breach involved a single employee device that was compromised through a poisoned VS Code extension. The company stated, “Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.” The activity appears to have been limited to the exfiltration of internal repositories, with GitHub assessing the number of affected repos to be approximately 3,800, consistent with the attacker’s claims.
GitHub has clarified that there is no evidence indicating customer data stored outside the affected repositories has been compromised. The company’s investigation remains active, and it has not yet attributed the attack to any specific threat actor. Meanwhile, cybercriminals associated with the TeamPCP hacker group claimed on a cybercrime forum to have accessed GitHub source code and roughly 4,000 private repositories, demanding at least $50,000 for the data. The group previously linked to supply chain attacks targeting developer platforms such as GitHub, PyPI, NPM, and Docker.
Why It Matters
This incident underscores the persistent security risks posed by malicious extensions in widely used developer tools. The breach demonstrates how a single compromised endpoint can lead to significant internal data exposure, potentially impacting thousands of organizations relying on GitHub. It raises concerns about supply chain security, insider threat mitigation, and the need for stricter controls over third-party extensions and employee device security practices.
As an affiliate, we earn on qualifying purchases.
Background
GitHub, owned by Microsoft, is the world’s largest platform for software development, hosting over 420 million repositories used by more than 180 million developers globally. Past incidents involving malicious VS Code extensions include malware that exfiltrated credentials or mined cryptocurrency, with extensions sometimes reaching millions of downloads before being removed. Supply chain attacks targeting developer ecosystems have increased in frequency and sophistication, exemplified by previous campaigns linked to the same hacker group, TeamPCP, which has targeted multiple code hosting and package management platforms.
“Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.”
— GitHub spokesperson
“We do not care about extorting GitHub, 1 buyer and we shred the data on our end, it looks like our retirement is soon so if no buyer is found we will leak it free.”
— Cybercriminals claiming on Breached forum
What Remains Unclear
It remains unclear whether the attacker has exfiltrated any other data beyond the internal repositories or if additional malicious activity occurred. The full scope of the breach and the identity of the threat actor are still under investigation, and there is no confirmation of whether customer data outside the affected repos has been compromised.
What’s Next
GitHub is continuing its incident response, monitoring for further malicious activity, and enhancing security protocols. The company is expected to update stakeholders as the investigation progresses and may implement additional security measures to prevent similar incidents in the future.
Key Questions
How did the breach happen?
The breach occurred when an employee installed a malicious VS Code extension that contained a trojan, which led to unauthorized access to internal repositories.
Has customer data been affected?
According to GitHub, there is no evidence that customer data stored outside the affected repositories has been impacted so far.
What is the hacker group claiming?
The hacker group TeamPCP claimed to have accessed around 4,000 private repositories and is demanding at least $50,000 for the data, though these claims are unverified.
What security measures are being taken?
GitHub has removed the malicious extension, isolated the compromised device, and is conducting a thorough investigation. Future security enhancements are likely to follow based on findings.
Source: Hacker News
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
