AI VS Code forks can prompt nonexistent Open VSX extensions
Overview
AI-powered VS Code forks (Cursor, Windsurf, Google Antigravity, Trae) inherit extension recommendations from Microsoft’s marketplace, but some recommended extension names don’t exist in Open VSX, the registry these forks rely on. This gaps creates a name-squatting avenue where attackers could publish malicious packages under those names; prompts can be file-based or software-based, increasing exposure.
All Sources
Articles
- https://thehackernews.com/
- https://www.secureblink.com/cyber-security-news/coinbase-phishing-scam-exploits-trust-in-email-infrastructure-to-hijack-crypto-wallets
- https://www.ideabrowser.com/previous-ideas
- https://radicaldatascience.wordpress.com/2026/01/05/ai-news-briefs-bulletin-board-for-january-2026/
- https://quantumzeitgeist.com/740-prediction-networks-domain-informed-link-advances-algorithms/
Story Timeline
AI VS Code forks can prompt nonexistent Open VSX extensions
AI-powered VS Code forks (Cursor, Windsurf, Google Antigravity, Trae) inherit extension recommendations from Microsoft’s marketplace, but some recommended extension names don’t exist in Open VSX, the registry these forks rely on. This gaps creates a name-squatting avenue where attackers could publish malicious packages under those names; prompts can be file-based or software-based, increasing exposure.