Key Takeaways
- A compromised employee workstation led to unauthorized access of approximately 3,800 GitHub internal repositories through a malicious VS Code extension
- Cybercriminal group TeamPCP has taken credit for the attack and is attempting to sell the exfiltrated data with a minimum asking price of $50,000
- Customer repositories, enterprise accounts, and organizational data remain unaffected according to GitHub’s investigation
- Changpeng Zhao, founder of Binance, issued an urgent warning for cryptocurrency developers to immediately rotate API credentials stored in code repositories
- GitHub has rotated essential credentials and continues active monitoring for suspicious activity across its infrastructure
GitHub has launched a comprehensive investigation into a security incident that resulted in unauthorized access to its internal code repositories. The breach originated from a compromised VS Code extension that was installed on an employee’s workstation.
[[TWITTER_0]]
The platform’s security team identified and neutralized the threat on Tuesday. Actions taken included removing the harmful extension, quarantining the compromised device, and activating emergency response protocols.
The breach resulted in exposure of roughly 3,800 internal repositories. GitHub has verified that this count matches the claims published by the threat actors responsible for the incident.
A cybercriminal collective known as TeamPCP has publicly claimed responsibility for the intrusion. The group is now marketing the stolen information on underground forums, alleging possession of approximately 4,000 repositories containing proprietary code from GitHub’s primary infrastructure and internal divisions.
TeamPCP operates as an advanced, automation-driven threat group specializing in targeting developer platforms to extract valuable credentials for monetary exploitation. Reports indicate the group has set a floor price of $50,000 for the compromised data.
Customer Information Remains Secure
According to GitHub’s ongoing investigation, there is no indication that customer data residing outside the company’s internal repositories has been compromised. All customer repositories, enterprise deployments, and organizational accounts appear to be unaffected.
The platform has already rotated essential security credentials, focusing first on those with the highest potential impact. GitHub’s security team continues examining system logs and maintaining surveillance for any additional suspicious behavior.
A comprehensive post-incident report will be released by GitHub upon completion of the investigation.
Urgent Alert for Cryptocurrency Developers
Binance founder Changpeng Zhao issued a swift response to the breach disclosure. He emphasized the critical importance of cryptocurrency developers rotating API keys that may be embedded in source code, including those in private repositories.
“If you have API keys in your code, even private repos, now is the time to double check and change them,” Zhao said.
Cryptocurrency developers depend extensively on GitHub for building and maintaining blockchain applications. Exchange API credentials, digital wallet access tokens, and infrastructure keys are frequently embedded in repositories for deployment in trading bots, automated scripts, and blockchain development tools.
Cybersecurity professionals recommend developers immediately audit their codebases for hardcoded secrets using specialized tools such as GitHub Secret Scanning, gitleaks, or Trivy. They further advise transitioning away from the practice of embedding sensitive credentials directly within source code repositories.
This security incident follows closely behind a separate attack at Grafana Labs, which disclosed a supply chain compromise on Tuesday. Attackers gained entry to Grafana’s GitHub repositories and issued ransom demands, which the company declined to fulfill.
The GitHub breach also surfaces shortly after the company disclosed CVE-2026-3854 on April 28, a critical security vulnerability. This flaw enabled authenticated users to execute arbitrary commands on GitHub’s server infrastructure and potentially exposed millions of public and private code repositories.
GitHub has committed to continuous monitoring of its systems and will provide regular updates as the investigation advances.





