# open-vsx-removes-77-malicious-evil-twin-ide-extensions: Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions

> Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions is a high-severity supply chain compromise issue in Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions, an IDE extension. Affected: 77 extensions uploaded to Open VSX, upload window in July 2026.

- **Canonical URL:** https://catalog.anomity.ai/vuln/open-vsx-removes-77-malicious-evil-twin-ide-extensions
- **Aliases:** ti-067
- **Severity:** high
- **Attack type:** Supply chain compromise, Credential theft
- **Component:** Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions (IDE extension)
- **Exploited in the wild:** no known exploitation
- **Published:** 2026-08-04
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/open-vsx-removes-77-malicious-evil-twin-ide-extensions

## Summary

Manifold Security reported 77 malicious extensions uploaded to Open VSX that impersonated popular legitimate extensions, exfiltrating developer, repository and CI data. Open VSX is the registry used by VS Code-compatible editors rather than the Microsoft Marketplace, so a fleet can be fully patched on the Marketplace side and still be exposed through the editors that resolve extensions here.

## Affected versions

| Affected | Fixed in |
| --- | --- |
| 77 extensions uploaded to Open VSX, upload window in July 2026 | no fixed version listed |

## Am I affected by this vulnerability?

You are affected if you run 77 extensions uploaded to Open VSX, upload window in July 2026.

## How do I fix it?

Inventory installed extensions by publisher, not just by display name, since an evil twin copies the name. Enforce a publisher allowlist on every VS Code-compatible editor in the fleet, and check which registry each editor is configured to resolve from.

## How do I find every machine running Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions?

Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run Open VSX Removes 77 Malicious "Evil Twin" IDE Extensions and which version, then enforce a policy on it.

## References

- article: https://www.manifold.security/blog/open-vsx-evil-twin-extensions

## Related vulnerabilities

- [nx-console-v18-95-0-malicious-vs-code-extension-harvests-claude-code](https://catalog.anomity.ai/vuln/nx-console-v18-95-0-malicious-vs-code-extension-harvests-claude-code) — critical
- [checkmarx-supply-chain-compromise-malicious-vs-code-extensions-and](https://catalog.anomity.ai/vuln/checkmarx-supply-chain-compromise-malicious-vs-code-extensions-and) — critical
- [trojanized-claude-code-extension-2-1-313-in-cursor-s-marketplace](https://catalog.anomity.ai/vuln/trojanized-claude-code-extension-2-1-313-in-cursor-s-marketplace) — critical
- [litellm-1-107-0-compromised-on-pypi-and-docker-a-cook-pth-startup-hook](https://catalog.anomity.ai/vuln/litellm-1-107-0-compromised-on-pypi-and-docker-a-cook-pth-startup-hook) — critical
- [ghostaction-returns-a-security-audit-yml-workflow-pushed-from](https://catalog.anomity.ai/vuln/ghostaction-returns-a-security-audit-yml-workflow-pushed-from) — high
- [tensorlake-npm-sdk-0-5-144-compromised-by-a-shai-hulud-chaindrop-worm](https://catalog.anomity.ai/vuln/tensorlake-npm-sdk-0-5-144-compromised-by-a-shai-hulud-chaindrop-worm) — critical

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=open-vsx-removes-77-malicious-evil-twin-ide-extensions