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.
this post was submitted on 14 Aug 2023
1119 points (100.0% liked)
Programmer Humor
853 readers
7 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Dream job.
Should've written the malware in Go, smh
Sorry, folks. Using cmalw-lib is now deprecated.
Cool kids are using systemd-malwd
Isn't this just a newer version of this? https://www.gnu.org/fun/jokes/evilmalware.html
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.
The newer one is a lot funnier though.
I guess the process could be regarded as gain of function research.
This reminds me of the old linux hater's blog post "At least we don't have any viruses".
That certainly was a blog with many emotions. Coming at this with no context, it looks like the kind of content that would be beautiful satire, except it's probably not.
Linux Hater's Blog was half satire and half honest criticism.
Seems like the prediction about the web panned out...
i laughed so hard 😂 😂 😂
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.