Meta discloses GitHub breach exposing code and data on 1,500 employees
Attackers using a stolen employee credential pulled source code and a small slice of personal data from Meta's GitHub repositories before being locked out.
What to know
- Meta is notifying roughly 1,500 people, mostly US employees, after hackers accessed its GitHub repositories using a stolen employee credential.
- Meta says 99% of the stolen material was business source code; the 1% personal data was mistakenly stored on GitHub in violation of company policy, and some of it was synthetic test data.
- Meta states its products and internal systems were not vulnerable or breached, and that it does not believe the attackers specifically targeted its data.
- Affected individuals are being offered credit and dark web monitoring; Meta has rotated exposed secrets and added new controls to keep user data off GitHub.
“We've since rotated secrets found in the repositories, implemented new controls to prevent user data from being stored in GitHub, and worked with GitHub on additional measures to protect our repositories.”
Meta spokesperson, Company spokesperson · SecurityWeek ↗ · Oct 12
Meta Breached companyMeta spokesperson Company representativeGitHub Platform providerUnnamed outside attacker group HackersEduard Kovacs SecurityWeek senior managing editor
How it unfolded 1 development · click the chart to see its coverage articlesposts
-
1
Social media amplifies and contextualizes the breach disclosure
Cybersecurity-focused accounts on X circulated the disclosure, with some framing it alongside other recent Meta employee-monitoring controversies.
“Meta confirmed hackers stole source code from their private GitHub repos using stolen employee credentials. also stolen: personal data on ~1,500 employees that was stored in the repo. against Meta's own policy.”
— @t3chfalcon -
Meta confirmed hackers stole source code from their private GitHub repos using stolen employee credentials. also stolen: personal data on ~1,500 employees that was stored in the repo. against Meta's own policy. so to recap Meta's 2026: — keystroke and mouse tracking program on all employees — t...
1 more of the top 2 · 2 posts in this stretch
-
🚨 BREAKING: Hackers broke into Meta's private GitHub repo and stole their source code. They got in with an employee's stolen credentials and took personal data on ~1,500 people, mostly US employees, stored there against Meta policy...
-
-
background
Meta spokesperson says no product or system was compromised — A Meta spokesperson characterized the incident as improper access to business data via stolen credentials rather than a vulnerability in any Meta product or breach of internal systems, and listed remediation steps taken.
-
background
Meta details split between stolen code and exposed personal data — Meta told SecurityWeek that 99% of the stolen material was business data in the form of software code, while the remaining 1% was personal data that had been improperly stored on GitHub in violation of company policy; some of that apparent personal data was actually synthetic or anonymized test data.
-
background
Meta begins notifying ~1,500 affected individuals — Notifications to the roughly 1,500 impacted people, most of them Meta employees in the US, started going out on Tuesday; affected individuals are being offered credit and dark web monitoring.
-
background
Meta shuts down attacker access, loops in GitHub and law enforcement — Meta's security team cut off the attackers' access to the repositories and brought in GitHub and law enforcement to investigate.
-
background
Outside group breaches Meta's GitHub repos with stolen credential — An outside group gained access to some of Meta's GitHub repositories using an employee's stolen login credentials; Meta detected the intrusion a few weeks before its public disclosure.
Also covered reported alongside — the timeline has no entry for these yet
-
first by Mastodon, 12h ago · also SecurityWeek
1 more headline