GitHub: Meta Says Hackers Took Code, Personal Data of 1,500 in GitHub Breach

GitHub: Meta Says Hackers Took Code, Personal Data of 1,500 in GitHub Breach

Meta Notifies 1,500 Individuals After GitHub Repository Breach Exposes Personal Data

Meta has begun notifying approximately 1,500 individuals primarily U.S.-based employees that their personal information was compromised after hackers accessed the company’s GitHub repositories using stolen employee credentials. The intrusion was detected a few weeks ago, prompting Meta’s security team to revoke the attackers’ access, engage GitHub and law enforcement, and initiate notifications on Tuesday.

According to Meta, 99% of the exfiltrated data consisted of business-related software code, while the remaining 1% included personal data that had been mistakenly stored in the repositories, violating company policy. The company clarified that much of the apparent personal data was synthetic or anonymized test data, making it difficult for attackers to distinguish genuine records. Meta does not believe the hackers were specifically targeting its data.

The breach did not stem from a vulnerability in Meta’s products or internal systems. Instead, the attackers exploited stolen credentials to access business data in GitHub repositories, which inadvertently included limited personal information. Meta has since rotated exposed secrets, strengthened product security controls, and implemented proactive scanning to prevent future accidental uploads of user data. The company is also working with GitHub to enhance repository protections and ensure compliance with its data storage policies.

Affected individuals are being offered credit and dark web monitoring services, and Meta has notified relevant regulators. The incident underscores the risks of credential-based attacks and the importance of enforcing strict data storage policies in development environments.

Source: https://www.securityweek.com/meta-says-hackers-took-code-personal-data-of-1500-in-github-breach/

GitHub cybersecurity rating report: https://www.rankiteo.com/company/github

"id": "GIT1791930487",
"linkid": "github",
"type": "Breach",
"date": "10/2026",
"severity": "25",
"impact": "1",
"explanation": "Attack without any consequences"
{'affected_entities': [{'customers_affected': '1,500 individuals (primarily '
                                              'employees)',
                        'industry': 'Technology/Social Media',
                        'location': 'U.S.',
                        'name': 'Meta',
                        'type': 'Company'}],
 'attack_vector': 'Stolen Credentials',
 'customer_advisories': 'Credit and dark web monitoring services offered to '
                        'affected individuals',
 'data_breach': {'data_exfiltration': 'Yes',
                 'number_of_records_exposed': '1,500 individuals',
                 'personally_identifiable_information': 'Yes (limited)',
                 'sensitivity_of_data': 'Low (mostly synthetic/anonymized test '
                                        'data)',
                 'type_of_data_compromised': ['Personal information',
                                              'Business-related software '
                                              'code']},
 'description': 'Meta has begun notifying approximately 1,500 individuals '
                'primarily U.S.-based employees that their personal '
                'information was compromised after hackers accessed the '
                'company’s GitHub repositories using stolen employee '
                'credentials. The intrusion was detected a few weeks ago, '
                'prompting Meta’s security team to revoke the attackers’ '
                'access, engage GitHub and law enforcement, and initiate '
                'notifications on Tuesday.',
 'impact': {'data_compromised': 'Personal information and business-related '
                                'software code',
            'identity_theft_risk': 'Yes',
            'systems_affected': 'GitHub repositories'},
 'initial_access_broker': {'entry_point': 'Stolen employee credentials'},
 'investigation_status': 'Ongoing',
 'lessons_learned': 'The incident underscores the risks of credential-based '
                    'attacks and the importance of enforcing strict data '
                    'storage policies in development environments.',
 'post_incident_analysis': {'corrective_actions': 'Rotated exposed secrets, '
                                                  'strengthened product '
                                                  'security controls, '
                                                  'implemented proactive '
                                                  'scanning, worked with '
                                                  'GitHub to enhance '
                                                  'repository protections',
                            'root_causes': 'Stolen credentials used to access '
                                           'GitHub repositories, accidental '
                                           'storage of personal data in '
                                           'repositories'},
 'recommendations': 'Enhance repository protections, enforce data storage '
                    'policies, and implement proactive scanning to prevent '
                    'accidental uploads of user data.',
 'references': [{'source': 'Meta Incident Notification'}],
 'regulatory_compliance': {'regulatory_notifications': 'Yes'},
 'response': {'communication_strategy': 'Notifications to affected individuals '
                                        'and regulators',
              'containment_measures': "Revoked attackers' access, rotated "
                                      'exposed secrets',
              'incident_response_plan_activated': 'Yes',
              'law_enforcement_notified': 'Yes',
              'remediation_measures': 'Strengthened product security controls, '
                                      'implemented proactive scanning to '
                                      'prevent accidental uploads of user data',
              'third_party_assistance': 'GitHub'},
 'title': 'Meta GitHub Repository Breach Exposes Personal Data',
 'type': 'Data Breach'}
Great! Next, complete checkout for full access to Rankiteo Blog.
Welcome back! You've successfully signed in.
You've successfully subscribed to Rankiteo Blog.
Success! Your account is fully activated, you now have access to all content.
Success! Your billing info has been updated.
Your billing was not updated.