LmCast :: Stay tuned in

GitHub Confirms Breach, 4K Internal Repos Stolen

Recorded: May 20, 2026, 8:58 p.m.

Original Summarized

GitHub Confirms Breach, 4K Internal Repos Stolen TechTarget and Informa Tech’s Digital Business Combine.TechTarget and InformaTechTarget and Informa Tech’s Digital Business Combine.Together, we power an unparalleled network of 220+ online properties covering 10,000+ granular topics, serving an audience of 50+ million professionals with original, objective content from trusted sources. We help you gain critical insights and make more informed decisions across your business priorities.Dark Reading Resource LibraryBlack Hat NewsOmdia CybersecurityAdvertiseNewsletter Sign-UpNewsletter Sign-UpCybersecurity TopicsRelated TopicsApplication SecurityCybersecurity CareersCloud SecurityCyber RiskCyberattacks & Data BreachesCybersecurity AnalyticsCybersecurity OperationsData PrivacyEndpoint SecurityICS/OT SecurityIdentity & Access Mgmt SecurityInsider ThreatsIoTMobile SecurityPerimeterPhysical SecurityRemote WorkforceThreat IntelligenceVulnerabilities & ThreatsRecent in Cybersecurity TopicsApplication SecurityGitHub Confirms Breach, 4K Internal Repos StolenGitHub Confirms Breach, 4K Internal Repos StolenbyAlexander CulafiMay 20, 20263 Min ReadCybersecurity OperationsInterpol's 'Operation Ramz' Pioneers Cross-Region Collabs in Middle EastInterpol's 'Operation Ramz' Pioneers Cross-Region Collabs in Middle EastbyRobert LemosMay 20, 20264 Min ReadWorld Related TopicsDR GlobalMiddle East & AfricaAsia PacificLatin AmericaSee AllThe EdgeDR TechnologyEventsRelated TopicsUpcoming EventsPodcastsWebinarsSEE ALLResourcesRelated TopicsResource LibraryNewslettersPodcastsReportsVideosWebinarsWhite Papers Partner PerspectivesDark Reading Resource LibraryApplication SecurityData PrivacyCyberattacks & Data BreachesVulnerabilities & ThreatsNewsGitHub Confirms Breach, 4K Internal Repos StolenOpen source software giant GitHub confirmed a data breach this week involving the theft of thousands of repos. One threat actor — TeamPCP — took credit.Alexander Culafi,Senior News Writer,Dark ReadingMay 20, 20263 Min ReadSource: Sundry Photography via Alamy Stock PhotoGitHub confirmed today it was breached via an attacker that stole thousands of internal repositories.TeamPCP, a financially motivated threat actor that has relentlessly targeted the open source ecosystem, yesterday published a post to a prominent Dark Web data breach forum that it would sell internal source code and organization data stolen from GitHub. This totaled "~4,000 repos of private code," according to the advertisement, and was for sale to an interested buyer. "As always this is not a ransom. We do not care about extorting GitHub, 1 buyer and we shred the data on our end, it looks like our retirement is soon so if no buyer is found we will leak it free," the post read.However, GitHub today partially confirmed the advertisement's claims in a series of posts on the official company account on X. According to the Microsoft-owned company, GitHub yesterday detected and contained the compromise of an employee device, which involved a poisoned VS Code extension. GitHub said it removed the malicious extension version, isolated the endpoint, and began incident response. Related:'Claw Chain' Vulnerabilities Threaten OpenClaw Deployments"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," the series of posts read. "We moved quickly to reduce risk. Critical secrets were rotated yesterday and overnight with the highest-impact credentials prioritized first. We continue to analyze logs, validate secret rotation, and monitor for any follow-on activity. We will take additional action as the investigation warrants. We will publish a fuller report once the investigation is complete."TeamPCP has become a force to be reckoned with for developers in recent months. Security experts have pinned the Shai-Hulud self-replicating worm attacks that began last year to TeamPCP, and it has further targeted organizations in credential attacks and more. Most recently, TeamPCP published the source code of Shai-Hulud to GitHub in an effort to spread the worm even further.GitHub Breach Begs: What Happened?The idea that TeamPCP would hit GitHub through a poisoned version of a Visual Studio Code (VS Code) extension (or perhaps a typosquatted application) is well within the threat actor's capabilities, as many of its recent campaigns have involved such threat activity.It is notable that the Microsoft-owned GitHub was compromised through a VS Code extension a year after GitHub committed itself to open source software security and two years after Microsoft committed itself to improved security practices. VS Code, a Microsoft format, isn't necessarily a Microsoft extension. So while breach victims deserve a bit of grace, the threat to the open source ecosystem has been well established for months. Related:Shai-Hulud Worm Clones Spread After Code ReleaseRoy Akerman, head of cloud and identity security for vendor Silverfort, tells Dark Reading that this attack happened because the trust model around developer tooling is "fundamentally broken.""A VS Code extension runs with the same privileges as the editor itself, and once installed it has access to everything the developer can reach," he says. "There's no meaningful verification before that code executes. What makes this breach remarkable isn't the entry point, it's that TeamPCP used GitHub's own infrastructure as the weapon end to end. They leveraged compromised developer tooling and trusted release workflows to distribute malicious code, including the poisoned VS Code extension that reached a GitHub employee's machine."Kayne McGladrey, senior member of the Institute of Electrical and Electronics Engineers (IEEE), echoed the concern about VS Code extensions running with full trust, "which means that they get access to the developer's filesystem, credentials, cloud keys, SSH keys, and environment variables." Related:Attackers Weaponize RubyGems for Data Dead DropsDark Reading contacted GitHub for additional comment.About the AuthorAlexander CulafiSenior News Writer, Dark ReadingAlex is an award-winning writer, journalist, and podcast host based in Boston. After cutting his teeth writing for independent gaming publications as a teenager, he graduated from Emerson College in 2016 with a Bachelor of Science in journalism. He has previously been published on VentureFizz, Search Security, Nintendo World Report, and elsewhere. At Dark Reading, he covers a variety of cybersecurity topics, including the cybercrime ecosystem, open source security, and the intersection between AI and threat actors. In his spare time, Alex hosts the weekly Nintendo podcast, "Talk Nintendo Podcast," and works on personal writing projects, including two previously self-published science fiction novels.He has received numerous awards, including TechTarget's Writer of the Year in 2022 as well as more than 10 Azbee awards for his reporting between 2022 and today. See more from Alexander CulafiWant more Dark Reading stories in your Google search results?Add Us NowMore InsightsIndustry ReportsHow Organizations Are Managing Incident ResponseHow Enterprises Are Developing Secure ApplicationsInside RSAC 2026: security leaders reveal the risks redefining your defense strategyHow Enterprises Are Harnessing Emerging Technologies in CybersecurityDitch the Data Center: Understanding Flexible Cloud Infrastructure Security ManagementAccess More ResearchWebinarsAI-Powered Cybersecurity for Resource-Constrained OrganizationsAI-Powered Credential Security: Intelligence Without ExposureHow Security Teams should apply Threat Intelligence into their DefensesYour Guide to Securing AI Adoption in Your OrganizationWhat is the Right Role for Identity Threat Detection and Response (ITDR) in Your Organization?More WebinarsEditor's ChoiceThreat IntelligenceFrom Stuxnet to ChatGPT: 20 News Events That Shaped CyberFrom Stuxnet to ChatGPT: 20 News Events That Shaped CyberbyDark Reading Editorial TeamMay 6, 202631 Min ReadCyber RiskPhysical Cargo Theft Gets a Boost From CybercriminalsPhysical Cargo Theft Gets a Boost From CybercriminalsbyRobert LemosMay 4, 20265 Min ReadWant more Dark Reading stories in your Google search results?Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.SubscribeRSAC 2026: key news & insightsAt RSAC 2026, Dark Reading captured critical intelligence on AI, new attack methods, geopolitics, and much moreGet Your RecapWebinarsAI-Powered Cybersecurity for Resource-Constrained OrganizationsThurs, June 18, 2026, at 1pm ESTAI-Powered Credential Security: Intelligence Without ExposureWed, June 17, 2026, at 1pm ESTHow Security Teams should apply Threat Intelligence into their DefensesThurs, June 11, 2026 at 1pm ESTYour Guide to Securing AI Adoption in Your OrganizationTues, June 9, 2026 at 1pm ESTWhat is the Right Role for Identity Threat Detection and Response (ITDR) in Your Organization?Wed, June 3, 2026 at 1pm ESTMore WebinarsBlack Hat USA | Mandalay Bay, Las VegasThe premier cybersecurity event of the year returns to Mandalay Bay with a re‑engineered, six‑day program built to ignite innovation, push boundaries, and bring the global security community together like never before. Use code: DARKREADING to save $200 on a Briefings pass or $100 on a Business pass.GET YOUR PASSDiscover MoreBlack HatOmdiaWorking With UsAbout UsAdvertiseReprintsJoin UsNewsletter Sign-UpFollow UsCopyright © 2026 TechTarget, Inc. d/b/a Informa TechTarget. This website is owned and operated by Informa TechTarget, part of a global network that informs, influences and connects the world’s technology buyers and sellers. All copyright resides with them. Informa PLC’s registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. TechTarget, Inc.’s registered office is 275 Grove St. Newton, MA 02466.Home|Cookie Policy|Privacy|Terms of UseYour Privacy Choices

Open source software giant GitHub confirmed a data breach involving the theft of thousands of internal repositories, with the threat actor TeamPCP claiming responsibility for the activity. TeamPCP posted on a data breach forum indicating they intended to sell internal source code and organizational data, though they stated they did not seek a ransom, offering to leak the data if no buyer was found. GitHub partially confirmed these claims, detailing that yesterday they detected and contained a compromise on an employee device resulting from a poisoned Visual Studio Code extension. GitHub subsequently removed the malicious extension version, isolated the endpoint, and initiated incident response protocols. The organization assessed that the activity involved the exfiltration of only GitHub-internal repositories, and the attacker's claim of approximately three thousand eight hundred repositories was directionally consistent with their findings. In response to this security event, GitHub prioritized rotating critical secrets, focusing on the highest-impact credentials, and continued to analyze logs for follow-on activity before releasing a fuller report.

The mechanism through which the breach occurred highlights deeper systemic vulnerabilities within the developer tooling ecosystem. Security experts suggest that the attack vector, involving a compromised Visual Studio Code extension, is feasible because such extensions often operate with the same privileges as the editor itself, granting access to everything the developer can reach without meaningful verification. As noted by Kayne McGladrey, a senior member of the Institute of Electrical and Electronics Engineers, extensions possess access to the developer's filesystem, credentials, cloud keys, SSH keys, and environment variables. This situation underscores the concern that the trust model surrounding developer tools is fundamentally broken. The remarkable aspect of the breach is not just the entry point but how the threat actor leveraged GitHub’s own infrastructure and trusted release workflows to distribute malicious code, including the poisoned extension, thereby weaponizing developer tooling to spread harmful code across the open source ecosystem.

TeamPCP has gained notoriety in recent months for targeting the open source community, with security experts linking them to attacks such as the Shai-Hulud self-replicating worm. This indicates an escalating threat where sophisticated threat actors are exploiting the inherent trust mechanisms embedded in software development workflows to achieve large-scale compromise. The incident emphasizes that securing the open source environment requires addressing the verification and trust mechanisms associated with the tools developers use daily, recognizing the vulnerability inherent in trusting code executed within these environments.