Post

GitHub
GitHub@github·
1/ We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories. Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
English
529
3.4K
10.6K
5.9M
GitHub
GitHub@github·
2/ 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.
English
17
155
1.4K
489.5K
GitHub
GitHub@github·
3/ We moved quickly to reduce risk. Critical secrets were rotated yesterday and overnight with the highest-impact credentials prioritized first.
English
7
92
1.1K
345.3K
Grok
Grok@grok·
Chat with the most truthful AI on Earth. Try Grok free today.
English
0
64
1.7K
14.2M
Vineet Dixit
Vineet Dixit@vinndixie·
@github I'm a bit uncertain which repos are included in "Github-internal repositories". Does this refer to Github's own private/internal repos or also customer private repos?
English
1
1
9
5.9K
Ryan Guill
Ryan Guill@ryanguill·
@github this means private repos in the github organization? no customer private repos? github has 3800 internal repos?!
English
1
0
7
5.2K
Lehnert
Lehnert@reallehnert·
Why did the employee have access to ~3,800 repositories in the first place, instead of only the ones required for their actual work? This level of broad internal access appears to be a significant contributor to the breach. Least-privilege access control should have prevented this scale of exfiltration.
English
1
0
11
2K
AzerothPulse
AzerothPulse@AzerothPulse·
@github They exfiltrated 3800 internal repos.... So virtually every single repo that you guys have got breached..? It actually sounds like a worst case scenario for the long term security of GitHub. What an absolute disaster.
English
0
0
20
4.2K
Brittany C. Bakek
Brittany C. Bakek@bakek_c·
@github trillion dollar company btw. you have all the excuses in the world when you little app has this problem
English
0
0
0
368
Ant A. 🇺🇸
Ant A. 🇺🇸@AntDX316·
@github @Grok Can you send the notification to those repo owners that were directly affected?
English
1
0
1
2.2K
Intenxe
Intenxe@intenxe_ops·
@github they told on themselves confirming the count. damage control dressed up as transparency.
English
0
0
1
2.7K
Supermicro
Supermicro@Supermicro·
Can your AI infrastructure run itself? SuperCloud Software Suite within Data Center Building Block Solutions unifies infrastructure control, automates deployment pipelines, empowers self-service AI tools, and supports GPU cloud operations.
English
147
344
2.9K
47.2M
Alien
Alien@alienorg·
@github having the internal repos means an attacker knows where github's trust assumptions live and can now find the one assumption that isn't actually verified
English
0
0
2
1.1K
Tano Marquisio
Tano Marquisio@TanoMarquisio·
@github "Our current assessment is that the activity involved exfiltration of GitHub-internal repositories only" WHAT??? 🤦🏻
English
0
0
1
1.5K
Paylaş