Key Takeaways
- A compromised employee device led to unauthorized entry into approximately 3,800 of GitHub’s internal repositories through a malicious VS Code extension
- Cybercriminal collective TeamPCP has taken credit for the attack and is attempting to auction the compromised information for a minimum of $50,000
- According to GitHub, no customer repositories, enterprise accounts, or organizational data were compromised in the incident
- Changpeng Zhao, founder of Binance, issued an urgent advisory for cryptocurrency developers to immediately replace API keys embedded in their code repositories
- GitHub has already replaced sensitive credentials and maintains active surveillance of its systems for any additional suspicious activity
GitHub is currently examining a cybersecurity incident following unauthorized penetration of its internal code storage systems. The breach originated from a compromised VS Code extension that was installed on a staff member’s computer.
[[TWITTER_EMBED]]The platform identified and neutralized the threat on Tuesday. Swift action included removing the harmful extension, quarantining the compromised machine, and initiating comprehensive incident response protocols.
The unauthorized access affected roughly 3,800 internal code repositories. GitHub has verified that this count matches the assertions made by the cybercriminal organization claiming responsibility.
A hacking collective identifying itself as TeamPCP has stepped forward to claim the operation. The group is now marketing the pilfered information on underground forums, alleging possession of nearly 4,000 repositories containing proprietary code from GitHub’s primary platform and internal organizational structures.
TeamPCP has been characterized as a highly sophisticated operation that leverages automation extensively, focusing on developer platforms to extract credentials for monetary benefit. Reports indicate the group is demanding no less than $50,000 for the stolen repository data.
User Information Remains Secure
GitHub’s forensic analysis has found no indication that customer data housed beyond its internal repository systems was affected. All customer code repositories, enterprise deployments, and organizational accounts remain uncompromised.
The company has already cycled through critical authentication credentials, focusing first on those with the most significant potential impact. Ongoing log analysis and infrastructure monitoring continue as preventive measures.
GitHub has committed to releasing a comprehensive incident report following the conclusion of its investigation.
Urgent Advisory for Cryptocurrency Developers
Binance founder Changpeng Zhao immediately addressed the situation. He issued a strong recommendation for cryptocurrency developers to immediately rotate all API keys stored within their codebases, regardless of repository visibility settings.
“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 their applications. Exchange API credentials, wallet access tokens, and infrastructure authentication keys are frequently embedded in repositories for deployment in trading bots, automated scripts, and blockchain applications.
Cybersecurity professionals are advising developers to conduct thorough scans for hardcoded sensitive information using security tools such as GitHub Secret Scanning, gitleaks, or Trivy. They’re also recommending a complete shift away from the practice of embedding credentials directly within code repositories.
This security incident follows another recent breach at Grafana Labs, which disclosed a supply chain compromise on Tuesday. In that case, attackers penetrated the company’s GitHub repositories and issued ransom demands, which the organization refused to pay.
The GitHub compromise also arrives soon after the April 28 announcement of a severe security flaw, CVE-2026-3854. That vulnerability permitted authenticated users to run arbitrary commands on GitHub’s servers, potentially exposing millions of both public and private code repositories.
GitHub has pledged to maintain continuous surveillance of its infrastructure and provide regular updates as the investigation advances.


