Skip to main content
Mallory
← Back to News
extension-plugin-hijackendpoint-software-vulnerabilitypersistence-methodinitial-access-method

VS Code Workspace Trust Bypass Enables Persistent Malicious Extension Installation

Supply Chain Risk · 3 sources · Updated 2mo ago · First seen Sep 17, 2026

VS Code Workspace Trust Bypass Enables Persistent Malicious Extension Installation

Researchers reported a Visual Studio Code Workspace Trust and Restricted Mode bypass in which a malicious repository can use a crafted command: link to invoke the internal workbench.extensions.installExtension command. If a developer Ctrl-clicks the link in VS Code’s raw source editor, the chain can install a local malicious .vsix package, activate it immediately, and persist across subsequent VS Code launches; the reported issue is that local VSIX packages are accepted without signature or publisher validation.

A malicious extension can execute JavaScript or TypeScript with the logged-in user’s privileges, putting developer files, credentials, and software-delivery infrastructure at risk. Organizations should keep Workspace Trust enabled, instruct developers not to open links in unfamiliar repositories, review installed extensions, and centrally restrict extension installation where possible. Disabling editor link detection with "editor.links": false is a temporary mitigation while command-link handling and extension-install controls are assessed.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events
  1. Reported Sep 19, 20262mo ago

    MSRC classifies VS Code Workspace Trust bypass as moderate

    According to the research, MSRC classified the reported VS Code Workspace Trust bypass as a moderate-severity Security Feature Bypass. No CVE had been assigned and no fix had been deployed at the time of publication.

    VS Code : contournement du Workspace Trust via un lien malveillant en un clic | CyberVeille
  2. Reported Sep 17, 20262mo ago

    Researchers report VS Code Workspace Trust bypass via command links

    Remedio researchers reported that a crafted `command:` link in a malicious Visual Studio Code project can invoke `workbench.extensions.installExtension` to install a local malicious VSIX package. The extension can activate immediately and persist across later VS Code sessions, potentially running with the logged-in user's permissions despite the workspace being untrusted.

    Visual Studio Code Vulnerability that Bypasses Workspace Trust : r/netsec
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Visual Studio Code
Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.