conv.

All stories
SecurityQuiet 11d · day 13

Major VS Code plugin compromised, pushes SSH backdoors

A trusted plugin from an established company was hijacked to distribute shell scripts installing remote access tools, validating long-standing security concerns.

newest coverage 11d agosummary written 10d ago5 pieces660 likes & upvotes32 comments Mastodon

What to know

  • A trusted VS Code plugin from an established company was compromised and used to distribute SSH backdoors, affecting developers who installed it.
  • The incident validates years of warnings from security researchers about VS Code's unsafe plugin architecture and Microsoft's refusal to implement restrictions.
  • Debate centers on whether the risk lies with VS Code's design or user responsibility, with skepticism that Microsoft will meaningfully address the underlying vulnerability.
most voices

VS Code's permissive plugin model is fundamentally unsafe and Microsoft must restrict it.

  • “we, people who like things to have some reasonable baseline amount of safety in our everyday tools, have been complaining for years that VS Code's plugin model is absurdly unsafe and an absolute open sewer”

    0xabad1dea · Mastodon ↗
some voices

The safest approach is to avoid third-party software altogether and only run code you write yourself.

  • “it is not only "not radical" but in fact "the only right choice" to only ever run software you yourself write, and to never connect such software to a network.”

    philip · Mastodon ↗

Microsoft VS Code maintainer0xabad1dea Security researcher

How it unfolded 2 developments, newest first · click a bar or a number to jump posts

Peak 2 pieces in 3h at Oct 30, 11 AM; 5 pieces over 13 days (5 posts) Oct 30, 8 AM — 1 piece · 1 post — Mastodon 1Oct 30, 11 AM — 2 pieces · 2 posts — Mastodon 2Oct 30, 2 PM — 1 piece · 1 post — Mastodon 1Oct 30, 5 PM — quietOct 30, 8 PM — quietOct 30, 11 PM — quietOct 31, 2 AM — quietOct 31, 5 AM — quietOct 31, 8 AM — quietOct 31, 11 AM — quietOct 31, 2 PM — quietOct 31, 5 PM — quietOct 31, 8 PM — quietOct 31, 11 PM — 1 piece · 1 post — Mastodon 1Nov 1, 1 AM — quietNov 1, 4 AM — quietNov 1, 7 AM — quietNov 1, 10 AM — quietNov 1, 1 PM — quietNov 1, 4 PM — quietNov 1, 7 PM — quietNov 1, 10 PM — quietNov 2, 1 AM — quietNov 2, 4 AM — quietNov 2, 7 AM — quietNov 2, 10 AM — quietNov 2, 1 PM — quietNov 2, 4 PM — quietNov 2, 7 PM — quietNov 2, 10 PM — quietNov 3, 1 AM — quietNov 3, 4 AM — quietNov 3, 7 AM — quietNov 3, 10 AM — quietNov 3, 1 PM — quietNov 3, 4 PM — quietNov 3, 7 PM — quietNov 3, 10 PM — quietNov 4, 1 AM — quietNov 4, 4 AM — quietNov 4, 7 AM — quietNov 4, 10 AM — quietNov 4, 1 PM — quietNov 4, 4 PM — quietNov 4, 7 PM — quietNov 4, 10 PM — quietNov 5, 1 AM — quietNov 5, 4 AM — quietNov 5, 7 AM — quietNov 5, 10 AM — quietNov 5, 1 PM — quietNov 5, 4 PM — quietNov 5, 7 PM — quietNov 5, 10 PM — quietNov 6, 1 AM — quietNov 6, 4 AM — quietNov 6, 7 AM — quietNov 6, 10 AM — quietNov 6, 1 PM — quietNov 6, 4 PM — quietNov 6, 7 PM — quietNov 6, 10 PM — quietNov 7, 1 AM — quietNov 7, 4 AM — quietNov 7, 7 AM — quietNov 7, 10 AM — quietNov 7, 1 PM — quietNov 7, 4 PM — quietNov 7, 7 PM — quietNov 7, 10 PM — quietNov 8, 1 AM — quietNov 8, 4 AM — quietNov 8, 7 AM — quietNov 8, 10 AM — quietNov 8, 1 PM — quietNov 8, 4 PM — quietNov 8, 7 PM — quietNov 8, 10 PM — quietNov 9, 1 AM — quietNov 9, 4 AM — quietNov 9, 7 AM — quietNov 9, 10 AM — quietNov 9, 1 PM — quietNov 9, 4 PM — quietNov 9, 7 PM — quietNov 9, 10 PM — quietNov 10, 1 AM — quietNov 10, 4 AM — quietNov 10, 7 AM — quietNov 10, 10 AM — quietNov 10, 1 PM — quietNov 10, 4 PM — quietNov 10, 7 PM — quietNov 10, 10 PM — quietYesterday, 1 AM — quietYesterday, 4 AM — quietYesterday, 7 AM — quietYesterday, 10 AM — quietYesterday, 1 PM — quietYesterday, 4 PM — quietYesterday, 7 PM — quietYesterday, 10 PM — quiet ◂ 1 earlier2
Oct 31Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6Nov 7Nov 8Nov 9Nov 10now · 12:10 AM ET
  1. 2

    Security researcher highlights years of unheeded warnings

    Infosec researcher notes that VS Code's unsafe plugin model has been criticized for years, with Microsoft consistently refusing to implement safety controls and deferring responsibility to users.

    “we, people who like things to have some reasonable baseline amount of safety in our everyday tools, have been complaining for years that VS Code's plugin model is absurdly unsafe and an absolute open sewer; Microsoft shrugs and says it's the user's responsibility…”
    — 0xabad1dea

    • RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 With every passing day I become increasingly emboldened that it is not only “not radical” but in fact “the only right choice” to only ever run software you yourself write, and to never connect such software to a network. (No, I haven’t written my own kernel yet despite thinking I maybe…

      philip@mallegolhansen.comMastodon11d agoview on Mastodon ↗
    2 more of the top 3 · 4 posts in this stretch
    • Aecernist@mastodon.social

      RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 I would politely suggest that any theft of crypto 'currency' is just fastracking what will eventually happen to all crypto 'currency'. The Microsoft scandal is small beans compared to the crypto-ponzi scandal.

      Aecernist@mastodon.socialMastodon12d agoview on Mastodon ↗
    • grumpybozo@toad.social

      RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 I’m pretty sure she knows this, but the audience should be warned: DO NOT HOLD YOUR BREATH WAITING FOR MICROSOFT TO ADDRESS THIS

      grumpybozo@toad.socialMastodon12d agoview on Mastodon ↗
    all of them →
  2. 1

    Major VS Code plugin compromised to distribute SSH backdoors

    A plugin from an established company was hijacked and began pushing shell scripts that automatically install SSH backdoors to infected machines.

    “a major plugin from a major company is compromised and begins pushing shell scripts to automatically install ssh backdoors…”
    — 0xabad1dea
    • 0xabad1dea@infosec.exchange

      okay, so here's what I'm thinking right now: 1) we, people who like things to have some reasonable baseline amount of safety in our everyday tools, have been complaining for years that VS Code's plugin model is absurdly unsafe and an absolute open sewer; Microsoft shrugs and says it's the user's responsibility to only install reliable plugins 2)…

      0xabad1dea@infosec.exchangeMastodon12d ago660▲view on Mastodon ↗

What people are saying 1 voices from 1 site · best of 5 · verbatim