This incident highlights the supply chain risks associated with developer tools like IDE extensions. It demonstrates the importance of rapid incident response, secret rotation, and endpoint isolation in mitigating the impact of a compromised internal environment.
On Monday May 18, we detected and contained a compromise of an employee device involving a poisoned VS Code extension published by a third party. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
Our current assessment is that the activity involved exfiltration of GitHub-internal repositories only. The attacker’s current claims of ~3,800 repositories are directionally consistent with our investigation so far.
We have no evidence of impact to customer information stored outside of GitHub’s internal repositories, such as our customer’s own enterprises, organizations, and repositories. Some of GitHub’s internal repositories contain information from customers, for example, excerpts of support interactions. If any impact is discovered, we will notify customers via established incident response and notification channels.
We moved quickly to reduce risk. We rotated critical secrets Monday and into Tuesday with the highest-impact credentials prioritized first.
We continue to analyze logs, validate secret rotation, and monitor our infrastructure for any follow-on activity. We will take additional action as the investigation warrants.
We will publish a fuller report once the investigation is complete.
The post Investigating unauthorized access to GitHub-owned repositories appeared first on The GitHub Blog.
Continue reading on the original blog to support the author
Read full articleSupply chain attacks exploit trust in package managers and CI/CD. These updates disrupt the attack lifecycle—from initial account compromise and 'pwn requests' to credential exfiltration—by enforcing stricter defaults, read-only caches, and secretless publishing.
Automated update tools often pull malicious code before it can be vetted. A mandatory cooldown period significantly reduces the risk of supply chain attacks by allowing time for the community to identify and pull poisoned releases from public registries.
Clear repository ownership is critical for security remediation and incident response. By automating ownership validation via custom properties, GitHub eliminated technical debt, archived thousands of stale repos, and ensured every active project has a direct point of contact.
False positives in security tools cause alert fatigue and erode developer trust. By using LLMs to understand code context, GitHub reduces noise by over 75%, ensuring engineers spend time fixing real vulnerabilities rather than triaging non-sensitive strings.
