GitHub breached via poisoned VS Code extension, 3,800 repos stolen


TL;DR

GitHub confirmed that the cybercrime group TeamPCP exfiltrated roughly 3,800 internal code repositories after compromising an employee device through a poisoned VS Code extension. The Microsoft-owned platform says no customer data was affected, but the breach highlights the growing threat of supply chain attacks targeting developer tools.

 

It is an unsettling irony when the world’s largest code-hosting platform becomes the victim of its own ecosystem. GitHub confirmed on Tuesday that a threat actor exfiltrated approximately 3,800 internal repositories after compromising an employee’s device through a poisoned Visual Studio Code extension, marking one of the most significant breaches the Microsoft-owned company has ever disclosed.

Github X post

Github X post

The cybercrime group TeamPCP, also tracked as UNC6780, claimed credit for the attack on the Breached hacking forum, where it offered the stolen data, which it described as proprietary source code and internal organisation files, for at least $50,000. The group said it would leak the material if no buyer materialised.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

GitHub’s investigation found that the breach began when an employee downloaded a malicious extension from the official VS Code Marketplace. That single installation was enough to give the attacker access to the employee’s device and, from there, to thousands of the company’s private repositories. GitHub said the attacker’s claim of roughly 3,800 repositories was “directionally consistent” with its own findings.

The company moved quickly once it detected the intrusion, isolating the compromised device, removing the extension, and rotating critical credentials within hours. GitHub stressed that the activity involved exfiltration of internal repositories only and that it had found no evidence of impact to customer data, enterprise accounts, or user-hosted repositories.

Still, the incident is a stark reminder of how supply chain attacks targeting developer tools can reach deep into even the most security-conscious organisations. TeamPCP has built a formidable track record in this space. The group was behind the compromise of Aqua Security’s Trivy vulnerability scanner earlier this year, an attack that ultimately led to the exfiltration of 92 GB of data from the European Commission’s AWS infrastructure. It has also targeted Checkmarx’s KICS, the LiteLLM AI gateway library, the Telnyx SDK, TanStack, and packages associated with MistralAI.

The VS Code Marketplace has become a growing vector for supply chain attacks. Unlike traditional package registries such as npm or PyPI, browser and editor extensions often receive broad system permissions by default, making them particularly attractive to attackers seeking lateral access. GitHub has not named the specific extension involved in its breach, and it remains unclear whether the extension was a newly published malicious listing or a compromised version of a legitimate tool.

The timing adds further pressure. GitHub’s breach arrives amid a broader surge in software supply chain compromises that have hit organisations across sectors. The ShinyHunters gang, which has collaborated with TeamPCP in the past, recently published stolen European Commission data. OpenAI was targeted through a compromised TanStack package. And earlier this month, researchers documented hundreds of malicious npm packages from a campaign dubbed Mini Shai-Hulud that was linked to the same threat cluster.

For GitHub, which hosts more than 100 million developers and serves as critical infrastructure for the global software industry, the breach raises uncomfortable questions about the security of the tools developers trust implicitly. If a platform built on code review and version control can be penetrated through a rogue extension, the implications for less security-mature organisations are sobering.

GitHub said its investigation is ongoing. It has engaged external forensics support and is working to determine the full scope of the data accessed. The company posted about the incident on X, reiterating that customer data remained unaffected.

TeamPCP, meanwhile, shows no signs of slowing down. From EU institutions to AI infrastructure to the backbone of open-source development itself, the group has demonstrated a consistent playbook: poison the tools that organisations depend on, and the perimeter becomes irrelevant.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


datafoundationgettyimages-1472653690

Eugene Mymrin/ Moment via Getty Images

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Trusted quality data is the backbone of agentic AI.
  • Identifying high-impact workflows to assign to AI agents is key to scaling adoption.
  • Scaling agentic AI starts with rethinking how work gets done. 

Gartner forecasts that worldwide AI spending will total $2.5 trillion in 2026, a 44% year-over-year increase. Spending on AI platforms for data science and machine learning will reach $31 billion, and spending on AI data will reach $3 billion.

The global agentic AI market will reach $8.5 billion by the end of 2026 and nearly $40 billion by 2030, per Deloitte Digital. Organizations are rapidly accelerating their adoption of AI agents, with the current average utilization standing at 12 agents per organization, according to MuleSoft 2026 research. This rate is projected to increase by 67% over the next two years, reaching an average of 20 AI agents. 

Also: How to build better AI agents for your business – without creating trust issues

According to IDC, by 2026, 40% of all Global 2000 job roles will involve working with AI agents, redefining long-held traditional entry, mid, and senior level positions. But the journey will not be smooth. By 2027, companies that do not prioritize high-quality, AI-ready data will struggle to scale generative AI and agentic solutions, resulting in a 15% loss in productivity. While 2025 was the year of pilot experiments and small production deployments of agentic AI, 2026 is shaping up to be the year of scaling agentic AI. And to scale agentic AI, according to IDC’s forecast, companies will need trustworthy, accessible, and quality data. 

Scaling agentic AI adoption in business requires a strong data foundation, according to McKinsey research. Businesses can create high-impact workflows by using agents, but to do so, they must modernize their data architecture, improve data quality, and advance their operating models. 

McKinsey found that nearly two-thirds of enterprises worldwide have experimented with agents, but fewer than 10% have scaled them to deliver measurable value. The biggest obstacle to scaling agent adoption is poor data — eight in ten companies cite data limitations as a roadblock to scaling agentic AI. 

Also: AI agents are fast, loose, and out of control, MIT study finds

McKinsey identified the top data limitations as primary constraints that companies face when scaling AI, including: operating model and talent constraints, data limitations, ineffective change management, and tech platform limitations. 

Data is the backbone of agentic AI

Research shows that agentic AI needs a steady flow of high-quality, trusted data to accurately automate complex business workflows. Successful agentic AI also depends on a data architecture that can support autonomy — executing tasks without human intervention. 

Two agentic usage models are emerging: single-agent workflows (one agent using multiple tools) and multi-agent workflows (specialized agents collaborate). In each case, agents will rely on access to high-quality data. Data silos and fragmented data would lead to errors and poor agentic decision-making. 

Four steps for preparing your data 

McKinsey identified four coordinated steps that connect strategy, technology, and people in order to build strong foundational data capabilities. 

Also: Prolonged AI use can be hazardous to your health and work: 4 ways to stay safe

  1. Identify high-impact workflows to ‘agentify’. Focus on highly deterministic, repetitive tasks that deliver value as strong candidates for AI agents. 

  2. Modernize each layer of the data architecture for agents. The focus on modernization should support interoperability, easy access, and governance across systems. The vast majority of business applications do not share data across platforms. According to MuleSoft research, organizations are rapidly adopting autonomous systems. The average enterprise now manages 957 applications — rising to 1,057 for those furthest along in their agentic AI journey. Only 27% of these applications are currently connected, creating a significant challenge for IT leaders aiming to meet their near-term AI implementation goals. 

  3. Ensure that data quality is in place. Businesses must ensure that both structured and unstructured data, as well as agent-generated data, meet consistent standards for accuracy, lineage, and governance. Access to trusted data is a key obstacle. IT teams now spend an average of 36% of their time designing, building, and testing new custom integrations between systems and data. Custom work will not help scale AI adoption. The most significant obstacle to successful AI or AI agent deployment is data quality, cited as the top concern by 25% of organizations. Furthermore, almost all organizations (96%) struggle to use data from across the business for AI initiatives.  

  4. Build an operating and governance model for agentic AI. This is about rethinking how work gets done. Human roles will shift from execution to supervision and orchestration of agent-led workflows. In a hybrid work environment, governance will dictate how agents can operate autonomously in a trustworthy, transparent, and scaled manner. 

The work assigned to AI agents 

McKinsey highlighted the importance of identifying a few critical workflows that would be candidates for AI agents to own. To begin, an end-to-end workflow mapping would help identify opportunities for agentic use. McKinsey found that AI adoption is led by customer service, marketing, knowledge management, and IT. It is important to identify clear metrics that validate impact. Teams should identify the data that can be reused across tasks and workflows.

Also: These companies are actually upskilling their workers for AI – here’s how they do it

McKinsey concludes that having access to high-quality data is a strategic differentiator in the agentic AI era. Because agents will generate enormous amounts of data, data quality, lineage, and standardization will be even more important in the agentic enterprise. And as agentic systems scale, governance becomes the primary level for control. The data foundation will be the competitive advantage in the agentic era. 





Source link