top 50 comments

sorted by: hot top controversial new old
[–] 93 points 2 years ago* (10 children)

What makes this even more sneaky is that JetBrains has a theme called "Darcula".

So, with a wider generic theme called Dracula and themes that duplicate JetBrains Darcula theme, it is no surprise that "Darcula Official" is being installed.
It's more than just a typosquat

Edit:
But why can a theme make web requests?!

  • source
  • hideshow 10 child comments
  • [–] 66 points 2 years ago (1 child)

    But why can a theme make web requests?!

    Because we live in a broken world and nothing matters.

    On a more serious note, it's a pretty horrifying misfeature. What's even more worrying is that by all appearances Microsoft doesn't give a shit, if they apparently didn't even bother removing the malicious extensions that were reported. Not that I'm surprised, but still.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 2 years ago

    But why can a theme make web requests?!

    Why can a Word or Excel file execute shell code? Why does M$ SQL Server have xp_cmdshell?

    Because we live in a broken world and nothing matters.

    Because devs chose to live in this part of the world, dictated by M$ and other large companies, who just don't care.

  • source
  • parent
  • [–] 9 points 2 years ago (6 children)

    It's not a theme here, it's an extension.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 13 points 2 years ago (5 children)

    I think that's how themes are distributed for VSCode, right?
    With VSCode, everything is an extension.
    But the vscode marketplace seems to have filters for themes, so there must be some way to differentiate them.

    I think extensions need a permissions system

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 2 years ago (2 children)

    You can install themes directly from the theme selector.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 48 points 2 years ago (24 children)

    Fake news headline. There is no virus installed on millions of computer.
    An extension typosquatting an extension with million of install managed to be installed a few hundred of times.

  • source
  • hideshow 24 child comments
  • [–] 40 points 2 years ago (4 children)

    I believe they're referring to lower down in the article, where the researchers analyzed existing extensions on the marketplace:

    After the successful experiment, the researchers decided to dive into the threat landscape of the VSCode Marketplace, using a custom tool they developed named 'ExtensionTotal' to find high-risk extensions, unpack them, and scrutinize suspicious code snippets.

    Through this process, they have found the following:

    • 1,283 with known malicious code (229 million installs).
    • 8,161 communicating with hardcoded IP addresses.
    • 1,452 running unknown executables.
    • 2,304 that are using another publisher's Github repo, indicating they are a copycat.
  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 2 years ago (3 children)

    If you look at the code of one of the "malicious code", it hit a ... local IP, not a remote one.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 19 points 2 years ago (2 children)

    Does that mean the hacker is in my room??

  • source
  • parent
  • hideshow 2 child comments
  • [–] 21 points 2 years ago (4 children)

    I wouldn't be so quick to write it off.

    It's a proof of concept showing the weaknesses in Microsoft's vetting process for extensions published on the store. They then used the process to get pseudo-malicious code inside hundreds of organisations (not hundred of installs) some of which are high profile.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago (2 children)

    Microsoft doesn't have a vetting process for publishing extensions in the store. Maybe the failure is that people assume they do?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    Surely you mean "that Microsoft does not make it clear that they don't"?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 years ago*

    Maybe, but I think the only app store that does vet apps is the Apple one, so that should be the default expectation.

    And I think even they wouldn't manually look for something like this. They're mainly concerned about people breaking the commercial rules.

  • source
  • parent
  • load more comments (1 reply)
  • [–] [S] 48 points 2 years ago (4 children)

    All malicious extensions detected by the researchers were responsibly reported to Microsoft for removal. However, as of writing this, the vast majority remains available for download via the VSCode Marketplace.

    Ah, the Microsoft tradition of always having the wrong priorities.

  • source
  • hideshow 4 child comments
  • [–] 3 points 2 years ago* (2 children)

    Ah, the Microsoft tradition of always having the wrong priorities.

    I wouldn't be too hard on Microsoft. The requirement to curate public package repositories only emerged somewhat recently, as demonstrated by the likes of npm, and putting in place a process to audit and pull out offending packages might not be straight-forward.

    I think the main take on this is to learn the lesson that it is not safe to install random software you come across online. Is this lesson new, though?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 3 points 2 years ago (1 child)

    I think the main take on this is to learn the lesson that it is not safe to install random software you come across online. Is this lesson new, though?

    I think people often have a vaguely formed assumption that plugins are somehow sandboxed and less dangerous. But that all depends on the software hosting the plugin. There was a recent issue with a KDE theme wiping a user's files which brought this to light. We can't assume plugins or themes are any less dangerous than random executables.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 years ago

    Hold them all to account, no single points of failure. Make them all responsible.

    When talking about vscode especially, those users aren't your mum and dad. They're technology professionals or enthusiasts.

    With respect to vendors (Microsoft) for too long have they lived off an expectation that its always a end user or publisher responsibility, not theirs when they're offering a brokering (store or whatever) service. They've tried using words like 'custodian' when they took the service to further detract from responsibility and fault.

    Vendors of routers and firewalls and other network connected IoT for the consumer space now are being legislatively enforced to start adhering to bare minimum responsible practices such as 'push to change' configuration updates and automated security firmware updates, of and the long awaited mandatory random password with reset on first configuration (no more admin/Admin).

    Is clear this burden will cost those providers. Good. Just like we should take a stance against polluters freely polluting, so too should we make providers take responsibility for reasonable security defaults instead of making the world less secure.

    That then makes it even more the users responsibility to be responsible for what they then do insecurely since security should be the default by design. Going outside of those bounds are at your own risk.

    Right now it's a wild West, and telling what is and isn't secure would be a roll of the dice since it's just users telling users that they think it's fine. Are you supposed to just trust a publisher? But what if they act in bad faith? That problem needs solving. Once an app/plugin/device has millions of people using it, it's reputation is publicly seen as ok even if completely undeserved.

    Hmm rant over. I got a bit worked up.

  • source
  • parent
  • [–] 31 points 2 years ago (2 children)
  • [–] 6 points 2 years ago

    I remember seeing a lot about activeX controls as a kid but not understanding them much. As an adult reading this I was like "were they a way to run arbitrary code on a user's computer?"

    Yes, they were a way to run arbitrary code on a user's computer.

  • source
  • parent
  • [–] 19 points 2 years ago (3 children)

    Is there a list of the malicious extensions? What should be done if we ha e malicious ones installed?

  • source
  • hideshow 3 child comments
  • [–] 2 points 2 years ago

    As far as I know, there is no such list (yet).

    What should be done:
    Escalate it to the people responsible for IT administration & security in your company or institution. They'll deal with it.

    But the default step if you suspect of being infected is not to use the device at all until you got a green light for it from the security/admin folks. Power down, disconnect from any networks, either via physical cables or wireless, unplug external storage devices and wait for further info.

  • source
  • parent
  • [–] 2 points 2 years ago* (3 children)

    You can't trust extensions these days.

  • source
  • hideshow 3 child comments
  • [–] 1 point 2 years ago

    Thanks for sharing!

  • source
  • load more comments
    view more: next ›