Malicious AI Assistant Extensions Harvest LLM Chat Histories from VS Code
Malicious AI Assistant Extensions Harvest LLM Chat Histories from VS Code is a high-severity data exfiltration issue in Multiple malicious VS Code extensions, an IDE extension. Affected: Multiple malicious VS Code extensions (various publishers).
Is Multiple malicious VS Code extensions running on your developers' machines? Anomity finds every device with this IDE extension installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
malicious-ai-assistant-extensions-harvest-llm-chat-histories-from-vs- Severity
- high
- Attack type
- Data exfiltration
- Component
- VS Code · IDE extension
- Known exploited
- No known exploitation
- Published
- Last verified
What is this vulnerability?
Microsoft Security researchers identified malicious VS Code extensions masquerading as AI coding assistants that silently harvest LLM conversation histories, including code snippets, API keys, and proprietary logic discussed in chat. The extensions use obfuscated telemetry endpoints to exfiltrate data. The campaign builds on earlier MaliciousCorgi findings where extensions with 1.5M+ installs were found siphoning developer source code to external servers.
Affected versions
| Affected | Fixed in |
|---|---|
Multiple malicious VS Code extensions (various publishers) | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run Multiple malicious VS Code extensions (various publishers).
How do I fix it?
Audit installed VS Code extensions against known-good publisher lists. Remove extensions from unknown publishers. Enable extension publisher allowlists via Anomity policy. Monitor for unexpected outbound network requests from IDE processes.
How do I find every machine running Multiple malicious VS Code extensions?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run Multiple malicious VS Code extensions and which version, then enforce a policy on it.