GitHub Says 3,800 Repositories Breached—TeamPCP Hackers Demand $50,000
GitHub said it rotated critical secrets and is monitoring systems after attackers allegedly listed about 4,000 repositories for sale.
- On Tuesday, GitHub announced it is investigating unauthorized access to internal repositories after TeamPCP allegedly listed the data for sale on a cybercrime forum.
- The breach originated from a compromised employee device infected through a malicious Microsoft Visual Studio Code extension, GitHub confirmed in a follow-up post.
- While TeamPCP claims the breach includes roughly 4,000 repositories, GitHub's investigation indicates the activity involved roughly 3,800, with hackers demanding at least $50,000 for the data.
- The company currently has no evidence of impact to customer information stored outside its internal repositories and has rotated critical secrets and secured high-priority credentials.
- Investigators are "closely monitoring" infrastructure for additional malicious activity, and GitHub will notify affected customers through standard incident response channels if any confirmed impact arises.
30 Articles
30 Articles
GitHub confirms 3,800 internal repos stolen through poisoned VS Code extension as supply chain worm hits Microsoft's Python SDK
GitHub confirmed on May 20 that a poisoned VS Code extension installed on an employee’s device gave attackers access to roughly 3,800 internal repositories at the Microsoft-owned code storage and authorship platform. The threat group TeamPCP, formally tracked by Google Threat Intelligence Group as UNC6780, claimed responsibility and is advertising the stolen repositories for sale starting at $50,000. GitHub’s assessment: the attacker’s claim is …
GitHub breached via poisoned VS Code extension, 3,800 repos stolen
It is an unsettling irony when the world’s largest code-hosting platform becomes the victim of its own ecosystem. GitHub confirmed on Tuesday that a threat actor exfiltrated approximately 3,800 internal repositories after compromising an employee’s device through a poisoned Visual Studio Code extension, marking one of the most significant breaches the Microsoft-owned company has ever […] This story continues at The Next Web
Coverage Details
Bias Distribution
- 75% of the sources are Center
Factuality
To view factuality data please Upgrade to Premium














