Lapsus$ claims GitHub internal compromise
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Lapsus$ ransomware gang claims compromise of GitHub with 299 employees and 2.5M user credentials exposed.
Ransomware.live, a public tracker of ransomware operator claims, reports that the Lapsus$ extortion group claims responsibility for a compromise of GitHub's internal systems. The claim includes metrics on compromised employee accounts (299), exposed user credentials (2.5 million), third-party employee credentials (117), and external attack surface findings (135). The report notes that Ransomware.live indexes only publicly visible claims by ransomware operators without accessing underlying stolen data. This represents a significant supply-chain and infrastructure threat if the claim is verified, as GitHub hosts critical software development assets for millions of organizations. Defenders should monitor for any official disclosure from GitHub and assess whether their organizations' repositories, secrets, or build pipelines may have been exposed.
Mentioned in this report
Detection guidance
1 detection for this report is in the app — rules that match its indicators, converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, plus YARA and Suricata. Three days of it free, no card.
Source reporting: https://www.ransomware.live/id/R0lUSFVCIElOVEVSTkFMQGxhcHN1cyQ=
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs