Command-grab-lnx-v1-1.zip May 2026

A few days ago, while digging through an old backup drive labeled “random_2007,” I found it. A single .zip file with a name that felt like a time capsule: command-grab-lnx-v1-1.zip .

But somewhere, on some forgotten IRC log or Slashdot thread from 2004, someone probably said: “Check out this command grabber I made. Works great on my colo box.” command-grab-lnx-v1-1.zip

I couldn’t resist. I unzipped it on an isolated VM. What I found wasn’t malware, nor a game. It was a strange, elegant, and almost forgotten piece of Linux history. Inside the zip was a single 32-bit ELF binary: grab . No man page. Running strings on it revealed a few clues: nc -l -p 31337 , /var/log/cmd.log , and a header: CMDGRAB v1.1 - (c) 2004 tty0n1n3 . A few days ago, while digging through an

You’ll hear the ghost of 2004 whisper back: ps aux . I never found the original author, tty0n1n3. The domain in the binary is dead. The email address bounces. Works great on my colo box

That’s why the zip file died out by v2.0. Real monitoring tools (Nagios, Zabbix, SNMP) won. And thank goodness.

command-grab solved a simple problem: “I want to see the live command history and process list of a remote box without logging in every 10 seconds.”

It was elegant. It was also terrifyingly insecure. Here’s the kicker: v1.1 had no authentication . Any packet to port 31337 would trigger the grab. If you ran this on a public server, anyone on the network could ask, “Hey, what commands are running right now?”