A reported Free Download Manager supply chain attack redirected Linux users to a malicious Debian package repository that installed information-stealing malware.

The malware used in this campaign establishes a reverse shell to a C2 server and installs a Bash stealer that collects user data and account credentials.

Kaspersky discovered the potential supply chain compromise case while investigating suspicious domains, finding that the campaign has been underway for over three years.

  • FredericChopin_@feddit.uk
    ·
    10 months ago

    How much faster are we talking?

    I’ve honestly never looked at my downloads and though huh you should be quicker, well maybe in 90’s.

    • arglebargle@lemm.ee
      ·
      10 months ago

      just grabbed a gig file - it would take about 8 minutes with a standard download in Firefox. Use a manager or axel and it will be 30 seconds. Then again speed isnt everything, its also nice to be able to have auto retry and completion.

    • TrustingZebra@lemmy.one
      ·
      10 months ago

      FDM does some clever things to boost download speeds. It splits up a download into different chuncks, and somehow downloads them concurrently. It makes a big difference for large files (for example, Linux ISOs).

      • FredericChopin_@feddit.uk
        ·
        10 months ago

        Im curious as to how it would achieve that?

        It can’t split a file before it has the file. And all downloads are split up. They’re called packets.

        Not saying it doesn’t do it, just wondering how.

        • everett@lemmy.ml
          ·
          10 months ago

          It could make multiple requests to the server, asking each request to resume starting at a certain byte.

            • drspod@lemmy.ml
              ·
              10 months ago

              The key thing to know is that a client can do an HTTP HEAD request to get just the Content-Length of the file, and then perform GET requests with the Range request header to fetch a specific chunk of a file.

              This mechanism was introduced in HTTP 1.1 (byte-serving).