This incident highlights the growing threat of supply chain attacks targeting developer tools. It underscores the need for robust endpoint security and rapid secret rotation protocols when internal source code is compromised to prevent lateral movement and further exploitation.
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’s internal repositories appeared first on The GitHub Blog.
Continue reading on the original blog to support the author
Read full articleBug bounty programs provide a critical feedback loop for hardening complex platforms. Understanding researcher methodologies, such as source-to-sink analysis and exploit chaining, helps engineers build more resilient systems and better anticipate sophisticated attack vectors.
Manual repository governance is a security risk and operational bottleneck. Evergreen shows how to automate access control and lifecycle management using native GitHub features and Git-based state, ensuring a fail-secure environment without complex external databases.
This update demonstrates how shifting from individual records to aggregate data can solve both performance bottlenecks and security risks. It shows the importance of aligning API design with actual user needs—tracking trends rather than identities—to improve system scalability.
