GitHub said on Tuesday it is investigating unauthorized access to its internal repositories after the threat actor TeamPCP claimed it was selling the platform’s source code and internal organizations, including about 4,000 repositories, for at least $50,000.
KEY FACTS
- Claim TeamPCP said it had GitHub source code and internal data for sale on a cybercrime forum.
- GitHub view The company said it has no evidence of impact to customer information outside its internal repositories.
- Compromise GitHub said it contained a compromise of an employee device tied to a poisoned Visual Studio Code extension.
- Response The company rotated critical secrets and said the activity appears limited to internal repositories.
In a disclosure on X, the Microsoft-owned company said it is monitoring for follow-on activity and will notify customers through established incident response and notification channels if it finds customer impact. The company said the attacker’s claims are directionally consistent with its investigation so far.
The post followed screenshots shared online that showed TeamPCP describing the sale as not being a ransom demand. In a follow-up message, the group said it would leak the data if no buyer was found.
GitHub said the compromised employee device involved a poisoned Microsoft Visual Studio Code extension, but it did not name the extension. The company said it had rotated critical secrets and was prioritizing the highest-impact credentials.
The disclosure came as TeamPCP’s broader Mini Shai-Hulud campaign continued to spread through open-source software. Google-owned Wiz said a separate case involved the durabletask Python package, where a compromised GitHub account was used to publish malicious versions that delivered a dropper and later-stage payload.
The package’s malicious code was designed to steal credentials from cloud services, password managers, SSH keys, Docker data and other secrets. The report said the stealer runs only on Linux systems, and other analysts said the worm can spread through AWS and Kubernetes environments.
WHY IT MATTERS
The case highlights how a single compromised account or endpoint can expose internal code and secrets and create wider supply chain risk. It also shows how stolen credentials can be reused to push malicious packages and expand an intrusion into developer and cloud environments.