AI VS Code forks push fake extensions, supply chain risk now

AI-powered VS Code forks recommended extensions missing from Open VSX, allowing attackers to claim unregistered namespaces and publish malicious packages that could expose secrets—vendors and the Eclipse Foundation have since implemented fixes and registry safeguards.

  • Several AI-powered forks of Microsoft Visual Studio Code (VS Code) recommended extensions that were not present in the Open VSX registry.
  • Unclaimed namespaces allowed anyone to register those extension names and upload packages, creating a supply-chain risk.
  • Attackers could publish malicious extensions that users install after seeing IDE recommendations, potentially exposing secrets and source code.
  • Vendors and the Eclipse Foundation implemented fixes and registry safeguards after responsible disclosure.

On Jan. 6, 2026, security researchers reported that AI-powered forks of Microsoft Visual Studio Code (VS Code) — including Cursor, Windsurf, Google Antigravity, and Trae — offered extension recommendations that did not exist in the Open VSX registry, creating a potential supply-chain risk, according to Malware“>Koi.

- Advertisement -

These IDEs inherit recommended extension lists from Microsoft’s marketplace. Recommendations appear in two ways: file-based prompts when opening certain file types, and software-based prompts when specific programs are installed on the host system.

Researcher Oren Yomtov described the core issue: “The problem: these recommended extensions didn’t exist on Open VSX.” Because the namespaces were unclaimed, anyone could register them and upload arbitrary packages to the registry.

As an example, an attacker could publish a package named ms-ossdata.vscode-postgresql. When a developer with PostgreSQL installed opens one of the affected IDEs, they might see “Recommended: PostgreSQL extension” and install the suggested package, which could execute malicious code and expose credentials, secrets, or source code.

Koi published placeholder packages to demonstrate the risk and reported that the PostgreSQL placeholder attracted about 500 installs. Other extension names claimed by Koi as placeholders included ms-azure-devops.azure-pipelines, msazurermtools.azurerm-vscode-tools, usqlextpublisher.usql-vscode-ext, cake-build.cake-vscode, and pkosta2005.heroku-command.

- Advertisement -

Following responsible disclosure, Cursor, Windsurf, and Google released fixes. The Eclipse Foundation removed non-official contributors from the registry and enforced broader safeguards. Developers are advised to verify publisher identities before installing recommended extensions.

✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.

Previous Articles:

- Advertisement -

Latest News

Idle GPUs Key to Easing AI Compute Crunch

GPU prices for AI workloads have surged dramatically, with the NVIDIA RTX 5090 up...

Base Ditches Optimism, AI Exploits Surge

Base, founded by Coinbase, is leaving the Optimism stack to build its own chain,...

Bitcoin Whales Amass Holdings While Exchange Outflows Spike

Large Bitcoin holders, or "whales," have rebuilt their reserves to levels last seen before...

MSTR Rebounds as Bitcoin Holds Above $67,000

MicroStrategy stock is up 8% this week to $132, signaling a potential rebound after...

Bitcoin surges after Supreme Court limits Trump tariffs

The Supreme Court ruled that most of President Donald Trump's tariffs were imposed by...

Must Read

How to Check The Rarity of An NFT

Whenever you invest in an NFT collection, you might have noticed that some NFTs are more expensive than others. NFT collections are often made...
🔥 #AD Get 20% OFF any new 12 month hosting plan from Hostinger. Click here!