Linux Virus Dependency Hell

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/lib 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 cmaw-lib-2.0. Turns out cmaw-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, grepped the Bitcoin wallet and sent $5 out of pity. 🔥 🌌 😁 💀

A Linux user describes painstakingly installing and debugging a supposed virus through missing permissions, dependencies, compilation, filesystem incompatibility, and a read-only partition. After all that effort, the virus crashes, so the user searches its source code, finds its Bitcoin wallet, and sends it $5 out of pity. The joke parodies the frustrations of Linux administration and treats malware like a struggling software project deserving charity. EN: A Linux user describes painstakingly installing and debugging a supposed virus through missing permissions, dependencies, compilation, filesystem incompatibility, and a read-only partition. After all that effort, the virus crashes, so the user searches its source code, finds its Bitcoin wallet, and sends it $5 out of pity. The joke parodies the frustrations of Linux administration and treats malware like a struggling software project deserving charity.

• @gentoomemes / 5902 2023-08-21
• @gentoomemes / 7049 2023-10-30
• @deenya_md / 23175 2026-01-30