• UnverifiedAPK@lemmy.ml
    116·
    11 months ago

    It’s like that guy that posted an example Bitcoin miner on GitHub, then a bunch of script kiddies forgot to change his wallet info for their own before deploying… He made a good chunk of change by doing nothing malicious.

  • douglasg14b@lemmy.world
    10911·
    11 months ago

    So, essentially, really poorly written malware? Given the number of assumptions it makes without any sort of robustness around system configuration it’s about as good as any first-pass bash script.

    It’d be a stretch to call it malware, it’s probably an outright fabrication to call it a virus.

      • Knusper@feddit.de
        321·
        11 months ago

        I wasn’t sure about it either. There’s security researchers out there who might genuinely want to get a virus to run in a VM.

        But yeah, the cmalw-lib-2.0 gives it away…

    • Isthisreddit@lemmy.worldEnglish
      1·
      11 months ago

      I know your shitposting, but I used to run into shit like this all the time back when I used to try to run Loki software games on Linux back in the day. Within 6 months all the games I had were un-fucking-runnable.

      It’s still a thing now depending how crazy you want to get with your system (let’s pretend you don’t run Linux on an x86 system for example - good luck lol)

      • Nato Boram@lemm.ee
        5·
        11 months ago
        Usage: ./malware [OPTIONS]

Options:
  -h, --help            Display this help message and exit.
  -i, --infect          Infect target system with payload.
  -s, --spread          Spread malware to vulnerable hosts.
  -c, --configure       Configure malware settings interactively.
  -o, --output [FILE]   Save log output to a file.
  -q, --quiet           Quiet mode - suppress non-critical output.

Advanced Options:
  -a, --activate [CODE] Activate advanced features with code.
  -b, --backdoor [PORT] Open backdoor on specified port.
  -m, --mutate          Evade detection by mutating code.

Description:
  Malware toolkit for educational purposes only.
  Use responsibly on authorized systems.

Examples:
  ./malware -i                  Infect local system with default payload.
  ./malware -i -s               Infect and spread to other systems.
  ./malware -a ACTCODE -b 1337  Activate advanced features and open backdoor.
  ./malware -q -o output.log    Run quietly, save logs to 'output.log'.
  • vsis@feddit.clEnglish
    31·
    11 months ago

    Sorry, folks. Using cmalw-lib is now deprecated.

    Cool kids are using systemd-malwd

    • chinpokomon@lemmy.ml
      13·
      11 months ago

      Even if it were inspired, it is significantly different the way it’s written. I’ve hit these same challenges before, so I’m more inclined to think it is independent discovery.

  • some_guy@lemmy.sdf.org
    10·
    11 months ago

    I laughed and my partner ask why. I told her it’s some really nerdy humor. She was fine not hearing the joke, but I loosely explained it anyway. She humored me anyway. She’s a good woman.

    • writeblankspace@lemm.ee
      1·
      8 months ago

      if only all my friends were like that

      They definitely tolerate my nerdiness, but they just don’t get it, even after an explanation.

  • Cwilliams@beehaw.org
    2·
    8 months ago

    Text version:

    Downloaded a virus for Linux lately and unpacked it. Tried to run it as root, didn’t work. Googled for 2 hours, found out that instead of /usr/local/bin the virus unpacked to /usr/bin for which the user malware doesn’t have any write permissions, therefore the virus couldn’t create a process file. Found patched .configure and .make files on some Chinese forum, recompiled and rerun it. The virus said it needs the library cmalw-lib-2.0.Turns out cmalw-lib-2.0 is shipped with CentOS but not with Ubuntu. Googled for hours again and found an instruction to build a.deb package from source. The virus finally started, wrote some logs, made a core dump and crashed. After 1 hour of going through the logs I discovered the virus assumed it was running on ext4 and called into its disk encryption API. Under btrfs this API is deprecated. The kernel noticed and made this partition read-only

    Opened the sources, grep’ed the Bitcoin wallet and sent $5 out of pity.