This is probably not the right community but I haven’t found a better one.

So I watched a video from Seytonic where he mentiond that some malware creates a windows link with the name of the usb on a usb. So I checked my usb because I remembered that I had to click 2 times on my usb to opened it. I found a link that contained cmd.exe and a name of a file next to it. Upload to the virustotal showed Raspberry Roblin worm.

I use Linux but my familly uses windows so I will have to go through all familly computers and remove the worm. Where can I find info how to remove this specific worm - Raspberry Roblin? On google I found a description about how the worm works but not specific files it creates and how to remove it.

The first page that shows up is microsoft.com and it says that windows defender detects the worm, but clearly it doesnt.

Edit: The worm was on one computer and it did not have windows defender installed. Seems like malware removed it and also disabled automatic updates. I installed MalwareBytes and sucessfully removed the worm :)

  • borari@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    10
    ·
    7 months ago

    To level set, Microsoft owns SysInternals, and has since 2006. None of it is “community vetted”, to me that implies FOSS or something.

    • Imprint9816@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      7 months ago

      Why would “community vetted” imply FOSS?

      Microsoft has a massive community of users and sysinternals is highly regarded amongst amateur and professional users alike. The term “community vetted” makes perfect sense in this context.

      • borari@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        7
        ·
        7 months ago

        Yeah, I use SysInternals stuff every day. Neither myself nor the community has vetted SysInternals tools any more than they have vetted outlook, teams, or word. Unless I’m misunderstanding the meaning of vetted.

        Vetting in a program/application context as I understand it is that the code has been vetted, which can only be done by the community at large if the source code is provided. Just like with a person, vetting is doing an actual background check, where as vouching for someone is just one person telling a second person that a third person is chill or something.