Post #149199

2026-01-22 12:40 UTC

That's it. I'm going back to Emacs. Threat Actors Expand Abuse of Microsoft Visual Studio Code https://www.jamf.com/blog/threat-actors-expand-abuse-of-visual-studio-code/

Replies (6)

@edcrypt@mastodon.coffee 2026-01-22 13:02

@rbanffy the other day I was trying ecode out https://github.com/SpartanJ/ecode

Open ##1991150
@revk@toot.me.uk 2026-01-22 13:37

@rbanffy I never embraced emacs... ed ... vi ... vim ... all the way. emacs vs vi was a culture thing at uni in the early '80s

Open ##1991152
@Enema_Cowboy@dotnet.social 2026-01-22 13:37

@rbanffy There's JetBrains Rider.

Open ##1991154
@benjamingeer@piaille.fr 2026-01-22 13:40

@rbanffy I switched from VSCode to Neovim last year and I've been very happy with it. I followed this guide: https://lazyvim-ambitious-devs.phillips.codes

Open ##1991165
@jmax@mastodon.social 2026-01-22 13:44

@rbanffy Which has basically the same vulnerability, for the same reasons. Been struggling with that since the 90s. [edit to add] Notwithstanding which, I am a dedicated Emacs user.

Open ##1991166
@neapel@mastodon.social 2026-01-22 13:51

seems hard to get past the first step (or really 3) of this attack though: getting someone to clone & open in VSCode & trust a random repo? Even if you don’t trust it, before long you’re probably running some of the arbitrary code inside manually?

Open ##1991167