Visual TL;DR
VS Code Extension CompromisedDriver
third-party VS Code extension published with malicious code
From the articleThe breach, detected on May 18th, originated from a poisoned VS Code extension published by a third party.
GitHub Internal Repos AccessedEffect
From the article 2 mentionsGitHub is investigating an unauthorized access incident that compromised its internal repositories.
Malicious Version RemovedOutcome
From the articleAccording to a blog post from the company, the malicious extension version was removed, and the affected employee device was isolated immediately.
Employee Device IsolatedOutcome
affected employee device was isolated to prevent further spread
From the articleAccording to a blog post from the company, the malicious extension version was removed, and the affected employee device was isolated immediately.
Internal Repos ExfiltratedEffect
activity involved exfiltration of GitHub-internal repositories only
No Customer Data ImpactOutcome
no evidence of customer data being affected outside internal systems
From the article 2 mentionsCrucially, the company states there is no evidence of impact to customer information stored outside of GitHub's internal systems, such as customer enterprises, organizations, and repositories.
Customer Support ExcerptsContext
From the articleHowever, some internal repositories did contain excerpts of customer support interactions.
Customer Notification PendingEffect
customers will be notified if any impact is discovered