Family
ksmd-ezo
A worm, an IRC bot and a miner, run by hand from a chat channel. The name is one we gave it here, for lack of a better one.
ksmd-ezo isn’t the name of a new family, nor one anyone else uses. It’s a homemade label. The pieces don’t fit neatly in any drawer: the oldest bot is a ShellBot, a public family that has been passed from hand to hand for decades; the new bot, the worm and the miner don’t resemble anything published that I’ve found, and antivirus engines barely see them or give them generic names. Since I don’t know exactly how to classify it, here we call it after the two pieces that define it: the worm that recruits, ksmd, and the bot that takes the orders, ezo. If it already has another name somewhere else, that one is worth more than ours.
The channel (chapter 38). A Perl IRC bot that obeys SEC and ZEC, on a custom-built server that scanners don’t see. A fleet of hundreds of business and government servers, and an operation that goes back at least to August, with three command servers along the way.
The worm (chapter 39). ksmd, in Rust: it tries passwords over SSH, discards routers and honeypots, logs every access in a collector before infecting and stops starting three days after being compiled. In September it was a Go program with the same rule.
The miner (chapter 40). labb, an XMRig installer in Go with a hunt for rival miners that can’t tell its own owner’s miner apart. The day it was rolled out, the operator lost command of about half the fleet. Behind it, two wallets on C3Pool, very probably belonging to the same operator.
- 38
Listening to SEC
For days, my probe gets the same visit every time: it comes in over SSH, asks what system it is and how many cores it has, and downloads a Perl script. That Perl script connects to a chat channel. I sat in the channel and listened to who was giving the orders, what the orders were, and how many machines were listening.
ksmd-ezo
2026-11 - 39
Expiry date
The package SEC hands out through the channel carries the program that was knocking on my door. It tries passwords, discards anything that smells of a honeypot, writes every access down on a separate machine before infecting, and carries its own expiry date inside. And the clock it was compiled with isn't the clock of the person who launches it.
ksmd-ezo
2026-11 - 40
Friendly fire
The third piece of SEC's kit is the one that gets paid: an installer written in Go with a Monero miner inside. Its new version has one more letter in its name and a hunt for rival miners. In my cage, the first thing it hunted down was my own instrumentation. In the botnet, it hunted down something else.
ksmd-ezo
2026-11