It took just one employee's stolen password for hackers to break into Meta's GitHub code repositories, in a security incident that has turned into an embarrassment for the company. The breach brought the personal information of approximately 1,500 Meta employees into play, with most of the affected staff reportedly based in the United States.

According to Meta's official statement, the attackers never gained access to the company's internal networks or servers. In other words, the intrusion targeted externally hosted code repositories rather than Meta's own systems.

What was actually leaked?

The bulk of what the hackers obtained was not personal data, but the company's software source code and trade secrets. Per the official breakdown, 99% of the data falls into that category, while only 1% consists of genuine personal information. A notable detail: that personal data had been accidentally uploaded to the GitHub repositories in the first place. So the issue isn't just a compromised password — sensitive information sitting in the wrong place is a security weakness of its own.

Real records were mixed with test data

Not every record in the leaked package corresponds to a real Meta employee. Some of the data came from anonymized or synthetic profiles created for software testing. That means a portion of the information in the hackers' hands doesn't belong to real people. But the presence of fake records doesn't change the fact that real employees' data was also stored in the repositories.

The company moved quickly

Once the leak was detected, Meta immediately revoked the attackers' repository access and launched a forensic investigation. Secret API keys were also rotated.

Affected employees were offered credit monitoring support to guard against identity theft, along with services that check whether their personal information is circulating on illegal platforms.

Even though internal systems were never reached, the loss of source code and some personal data to hackers is a serious warning for Meta. And the information accidentally uploaded to the repositories exposes yet another weak link in the security chain.