Victim Claim
GITHUB INTERNAL
Claimed by
lapsus$
Listed on leak site
13 Jun 2026
Reported attack date
19 May 2026
Group claims tracked
7
Unverified claim.
This entry reproduces a listing published by the lapsus$ group on its own extortion site.
Attackers routinely exaggerate or fabricate victims. Nothing here confirms that
GITHUB INTERNAL suffered a breach, or what data was actually taken.
About the organisation
Everything for the main platform is there. No ransom, we do not care about extorting Github. If no buyer is found, we leak for free.
What the listing means
GITHUB INTERNAL appeared on the lapsus$ leak site on 13 June 2026. Groups publish a victim once negotiations stall or as pressure during them, so a listing usually means data was already exfiltrated — the attack itself is dated 19 May 2026, 25 days before the listing. This group has not published new claims in the last 30 days.
Recommended actions
- Treat any unsolicited message referencing GITHUB INTERNAL as suspicious — leaked data gets weaponised for phishing within days.
- If you hold an account on github.com, change that password now, update it anywhere you reused it, and enable two-factor authentication.
- Other Technology organisations should review this group's known TTPs and validate detection coverage against them.
- Watch for follow-on extortion: stolen data is often re-leaked or resold after the initial listing.
- A leak-site listing is a claim made by the attacker, not a confirmed breach — check the organisation's own disclosures before acting on it.
Leak-site evidence
Listing URL https://www.ransomware.live/id/R0lUSFVCIElOVEVSTkFMQGxhcHN1cyQ=