<![CDATA[Malicious VS Code extensions strike again.]]>Malicious VS Code extensions strike again. I’ve lost track of how many times this has happened.

X Cancelled | Verifying your request

favicon

(xcancel.com)

]]>https://board.circlewithadot.net/topic/adb4e4b0-05ed-4ff4-8ec8-1caf7790723e/malicious-vs-code-extensions-strike-again.RSS for NodeMon, 25 May 2026 10:38:22 GMTWed, 20 May 2026 06:50:29 GMT60<![CDATA[Reply to Malicious VS Code extensions strike again. on Wed, 20 May 2026 07:45:52 GMT]]>Now is a good time to remind everyone that there has been an open request since 2018 to harden how VS Code extensions are run, and Microsoft has yet to address it

Link Preview Image
[Feature Request] Extension Permissions, Security Sandboxing & Update Management Proposal · Issue #52116 · microsoft/vscode

I believe that Visual Studio Code should support some kind of "Extension Permission Management", complete with prompts, warnings, opt-in, and opt-out, similar to what has been supported for some time now with Chrome, Firefox, and other b...

favicon

GitHub (github.com)

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/agnivesh/statuses/116605789959904982https://board.circlewithadot.net/post/https://infosec.exchange/users/agnivesh/statuses/116605789959904982Wed, 20 May 2026 07:45:52 GMT<![CDATA[Reply to Malicious VS Code extensions strike again. on Wed, 20 May 2026 06:56:30 GMT]]>@agnivesh Friends don’t let friends use Visual Studio Code.

]]>https://board.circlewithadot.net/post/https://cotorreo.fraggle-rock.org/users/mokey/statuses/01KS22QVZR2BE3B7S1D998WQP5https://board.circlewithadot.net/post/https://cotorreo.fraggle-rock.org/users/mokey/statuses/01KS22QVZR2BE3B7S1D998WQP5Wed, 20 May 2026 06:56:30 GMT