3,800 internal GitHub repositories were stolen: Detailed explanation of the TeamPCP attack

On May 20, 2026, GitHub disclosed that its internal warehouse was invaded by the TeamPCP organization, and about 3,800 private warehouse source codes were stolen. The attacker has previously created Shai-Hulud npm supply chain attacks. There is currently no conclusive evidence that customer data was affected.

Core conclusion

On May 20, 2026, GitHub disclosed a serious security incident through the official X account: an attacker successfully invaded GitHub's internal warehouse system and stole the source code of approximately 3,800 private warehouses. The attackers were identified as TeamPCP – the same team responsible for the Shai-Hulud npm supply chain attack.

Key Points

Event Time: 2026-05-20
Scope of Impact: About 3,800 GitHub internal private repositories were stolen
Attacker: TeamPCP (Creator of Shai-Hulud malware)
Customer Data Security: GitHub says there is currently no evidence that customer data was affected
Current Status: The investigation is ongoing and the root cause has not yet been announced

Event history

On May 20, GitHub issued an official statement through the X platform, confirming that it was investigating an unauthorized access incident to its internal warehouse. The statement mentioned:

"We are investigating unauthorized access to internal GitHub repositories. There is currently no evidence that customer information, including the enterprise's code repositories and organizational data, was affected, but we are closely monitoring our infrastructure to prevent further activity."

Later, GitHub released a second update confirming that the attackers claimed to have stolen approximately 3,800 internal repositories, "generally consistent with our current findings."

Summary of key information

Dimensions	Details
Attack time	2026-05-20
Attacker identity	TeamPCP (Shai-Hulud organization)
Stealing data	~3,800 internal repository source codes
Customer Impact	There is currently no evidence that customer warehouses have been affected
Attack method	Still under investigation, specific entrance unknown
Current status	Under investigation, evidence is not fully controlled

Attacker background: TeamPCP and Shai-Hulud

TeamPCP is one of the most active software supply chain attack groups in recent years. In April this year, the organization launched a large-scale poisoning attack on the npm ecosystem through the Shai-Hulud malware—poisoning 317 npm packages in 22 minutes, which once caused widespread panic in the open source community.

In this attack on GitHub's internal warehouse, TeamPCP has obviously upgraded its goal from "poisoning open source packages" to "stealing the core code of the platform." This means that attackers may have more powerful attack capabilities and entrances than before.

Impact on developers and enterprises

What GitHub users need to know

Your Code is Safe: There is currently no indication that customer data from public or private repositories has been stolen
API Token rotation recommended: As a precautionary measure, GitHub users are advised to rotate their current Personal Access Token and OAuth Token
Watch for follow-up announcements: GitHub expects to release a more detailed incident report upon completion of the investigation

CI/CD Security Implications

This incident once again highlights the importance of internal system security protection:

Principle of Least Privilege: Internal warehouse access should be isolated from security systems
Monitor abnormal access: The access logs of internal warehouses should be used for abnormal detection
Code is an asset: The source code library should be regarded as a core asset and configured with the same level of protection as the security system

CI/CD

Community reaction and concerns

The response of the HN community to this incident showed several main directions of discussion:

**Is it appropriate to publish security advisories only through
The frequency of security incidents is rising — As AI coding capabilities improve, automated attacks are increasing in complexity and frequency
Should enterprises re-evaluate their code hosting strategies — Increased focus on self-hosted Git services (e.g. Gitea, GitLab Self-Managed)

Related extended information

Internal link guidance

Want to know more about AI supply chain security? See: How to add quality gates to your AI automation workflow: A practical guide from output to trustworthy results
Real case: The open source tool Postiz doubled its revenue by relying on n8n security compliance: Open source social media tool doubles revenue with n8n node: review of growth from $6,500 to $12,600/mo
Security practices in AI Agent automation: AI Agent drives automated website operations: Build a fully automatic content pipeline in 30 minutes