this post was submitted on 01 Mar 2025
24 points (100.0% liked)

VS Code

867 readers
2 users here now

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Kelly@programming.dev 5 points 1 week ago (2 children)

"We just had an outdated sanity.io dependency used since 2016 to show release notes from sanity headless CMS, that was the only issue they found."

"That dependency has been there since 2016 and passed every check since then, now it looks compromised but NO ONE from Microsoft reached us to remove it. They just pulled down everything causing issues to millions of users, and causing a loop in vscode (yep, it's their fault)"

If the dependency has been compromised then extensions that use that dependency and ship compromised code are also compromised. Its a transitive property if it ships bad code.

With that in mind Microsoft yoinking the extension from the market place and user devices seems reasonable. But what was the "loop" they mention?

[–] Novack@programming.dev 2 points 6 days ago* (last edited 6 days ago)

From user devices? I for sure, dont want Microsoft to do nothing on my devices. My device, my place, my decision.

[–] Kissaki@programming.dev 10 points 1 week ago (1 children)

But what was the “loop” they mention?

The linked issue comment has the info about it

Letting you know that VSCode is unable to uninstall the extension. It prompts me to uninstall, but when I confirm the window refreshes and the extension is still there, triggering the same "is problematic" prompt. This is an infinite loop. Same behavior when trying to uninstall the usual way from the extensions panel.

[–] Kelly@programming.dev 5 points 1 week ago

Well that's not ideal.