Skip to main content

GitHub Breach Tied to Malicious VS Code Extension Exposes Thousands of Internal Repositories

GitHub says attackers accessed thousands of internal repositories after a company employee’s device was compromised through a malicious Visual Studio Code extension, though the company said it has removed the malicious extension, isolated the compromised endpoint, and launched an investigation.

The company confirmed that approximately 3,800 internal repositories were affected. GitHub stated that investigators have not found evidence of impact to customer repositories or enterprise environments outside GitHub’s own systems.

The hacking group TeamPCP later claimed responsibility for the intrusion in a post on the Breached cybercrime forum. The group alleged it had obtained source code and thousands of private repositories and sought at least $50,000 for the data.

GitHub has not formally attributed the attack to TeamPCP, though the company acknowledged that the group’s public claims are generally consistent with the scope of the ongoing investigation.

The GitHub breach is the latest example of the increasing attacks against software development infrastructure. Hackers view developer platforms as efficient paths into enterprise systems because a single compromise can create downstream access across multiple companies.

GitHub said it continues to review logs, rotate credentials and monitor for additional malicious activity tied to the incident. The company said it plans to publish a more detailed report once its investigation is complete.

Protecting Dev Tools

Enterprise security teams are facing a growing challenge these days: protecting not only production systems, but also the interconnected tools that developers are using. Over the past several years, malicious extensions and backdoored open source packages have been used to distribute credential stealers and ransomware.

Visual Studio Code extensions are commonly used to add features and integrations to Microsoft’s widely adopted code editor. Because these extensions often operate with elevated permissions inside development environments, compromised plugins can provide attackers with access to internal systems.

Earlier incidents involving the VS Code marketplace included extensions masquerading as legitimate developer tools that secretly harvested credentials or deployed malware. In January, researchers identified malicious AI-themed coding assistant extensions that reportedly transmitted data from compromised systems to infrastructure located in China.

TeamPCP has emerged as a notable actor in software supply chain attacks targeting open source ecosystems. Researchers have linked the group to campaigns involving GitHub Actions workflows, npm packages, Docker environments and PyPI repositories.

Several of those operations focused on stealing sensitive developer information including SSH keys, Kubernetes configurations and cloud credentials. Researchers have also connected the group to compromised software packages distributed through legitimate repositories and typosquatting campaigns designed to trick developers into downloading malicious code.

The risk of attacks has expanded further as companies adopt AI-assisted coding tools and open source dependencies to accelerate software development. Many enterprises now rely on large ecosystems of third-party plugins and extensions that can introduce additional security exposure.



from DevOps.com https://ift.tt/GTPwYnL
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

OpenAI Debuts Symphony to Orchestrate Coding Agents at Scale

OpenAI has unveiled Symphony, an open-source specification that shifts how software development teams deploy AI in workflows, moving from interactive coding assistance toward continuous orchestration of autonomous agents. Symphony reframes project management tools as operational hubs for AI-driven coding. Rather than prompting an assistant for individual tasks, developers assign work through issue trackers, allowing agents to execute tasks in parallel and deliver outputs for human review. The change reflects a trend in enterprise AI in which systems are increasingly embedded into production pipelines rather than used as standalone tools. Symphony emerged from internal experimentation at   OpenAI , where engineers attempted to scale the use of   Codex   across multiple concurrent sessions. While the agents proved capable, human operators became the limiting factor. Engineers found they could only manage a handful of sessions before coordination overhead offset pro...
Post a Comment
Read more