![](\"https:\/\/nuxx.net\/blog\/wp-content\/uploads\/2026\/06\/katester_hack_whenfound.png\")
Something isn’t right…<\/center><\/p>\nThis afternoon, not long before leaving work, I just happened to check out bandwidthd<\/a> running on nuxx.net<\/a>. I was a bit surprised that it looked like this<\/a>.<\/p>\n Yes, something was hacked. So, what happened?<\/p>\n Well, the first thing I did was just run top<\/tt> as root to see if anything stood out. The first thing I saw was the user katester<\/tt> running perl<\/tt> and taking up loads of CPU, having consumed something like 26 hours of CPU time. In short: ack!<\/p>\n Next I took a quick stab at what was doing it…<\/p>\n root@rowla:~# ps auxw | grep katester | grep perl Well, there’s the culprit… So, I killed it off, and it didn’t come back. Traffic immediately went back to normal, as can be seen here<\/a>, in a mirror taken a bit after fixing things.<\/p>\n root@rowla:~# kill 23802<\/tt><\/p>\n Next I shut down all of the sites owned by katester<\/tt> by commenting out their includes in the lighttpd<\/a> config file and then restarting lighttpd.<\/p>\n Not finding any copies of udp.pl<\/tt> anywhere on the box, with nothing weird beneath \/tmp<\/tt> or ~katester<\/tt> I threw udp.pl<\/tt> into Google<\/a>. There were a few results, most of them showing this file<\/a>, which appears to be a tool for DOSing boxes rather inefficiently by throwing random data at a port.<\/p>\n One of the next things I saw were two zombie processes and a copy of bash<\/tt> running as katester<\/tt>, along with the PHP<\/a> processes normally allocated to that account:<\/p>\n root@rowla:~katester# ps -U katester I noticed (but didn’t capture) that the copy of bash<\/tt> there was started at the same time as udp.pl<\/tt>. Because I was trying to isolate this user as much as possible I went ahead began killing off the PHP processes. As soon as I killed 59959<\/tt> the next one, 67261<\/tt> died as well. I then noticed that bash<\/tt> and both of the zombies were gone.<\/p>\n Now I figured it was time to start looking for where the infection came from so I could get the four downed sites back up as soon as possible. I just simply used grep to look through the httpd’s log files for things occurring during 13:00:00 EDT on 05-Sep-2007. (I also checked the 12:00:00 and 14:00:00 blocks and didn’t see anything suspectious.) After a few moments I noticed this:<\/p>\n 142.166.3.123 www.katester.net - [05\/Sep\/2007:13:37:02 -0400] \"GET \/blog\/index.php\/feed\/ HTTP\/1.1\" 200 17637 \"-\" \"radianrss-1.0\"<\/tt><\/p>\n Throwing radianrss-1.0<\/tt> into Google gave me no results, which is more than a little suspicious for what sounds like an RSS reader’s useragent. I looked through the other logs for the site and I could see other visits from 142.166.3.123<\/tt> and found something interesting.<\/p>\n I next went ahead and called the site’s owner, discussed it with her, archived ...\/blog<\/tt>, and deleted that directory from the server. I was then able to bring the katester<\/tt> PHP processes and sites back online.<\/p>\n While there were other visits from 142.166.3.123<\/tt> accessing \/blog\/index.php\/feed\/<\/tt>, every other one before that time had a useragent of Jakarta Commons-HttpClient\/3.1-beta1<\/tt>. Here’s an example:<\/p>\n 142.166.3.123 www.katester.net - [05\/Sep\/2007:03:19:47 -0400] \"GET \/blog\/index.php\/feed\/ HTTP\/1.1\" 200 17637 \"-\" \"Jakarta Commons-HttpClient\/3.1-beta1\" Then, next was the first entry with the odd useragent. All right around the time things began, and nothing else from that IP but those specific requests. I’ve now got tcpdump<\/a> running, listening for anything from that IP, so I can (hopefully) see exactly what the malicious request was. There have been other requests since yesterday afternoon with the same radianrss-1.0<\/tt> useragent, so I expect (and hope) the exploit will be attempted again.<\/p>\n Here’s what I suspect happened:<\/p>\n · The copy of WordPress<\/a>, known for it’s numerous security holes, which happened to be running on katester.net<\/a> was somehow exploited. I suppose in the future that I could have left udp.pl<\/tt> running for a little longer so that I could better investigate it, but I didn’t want to allow the DOSing that was happening to continue.<\/p>\n As some of you probably remember, back on 08-Jul-2006<\/a> the then-server hosting nuxx.net<\/a> and many other sites was compromised. That happened because I had all the vhosts, PHP, and the httpd running as the same user with one of those vhosts running an old, vulnerable copy of phpBB<\/a>. When things finally settled down and I moved to the new box I was able to run the httpd as its own user, with separate banks of PHP processes running for each user. Each user’s files were also held under their own home directories with accessible, but not modifiable (by the user) log files.<\/p>\n While the exploiting script last time was able to access (and delete) the contents of all the root directories of each user’s website, the more-proper privilege separation in new configuration mitigated potential risk. Fortunately it appears that this attack did little more than DOS an IRC server, but had it tried to do more it’s nice to know that it would have likely been contained to just ~katester<\/tt>.<\/p>\n","protected":false},"excerpt":{"rendered":" Something isn’t right… This afternoon, not long before leaving work, I just happened to check out bandwidthd running on nuxx.net. I was a bit surprised that it looked like this. Yes, something was hacked. So, what happened?<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,34],"tags":[],"class_list":["post-8960","post","type-post","status-publish","format-standard","hentry","category-computers","category-moved-from-livejournal"],"_links":{"self":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/8960","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/comments?post=8960"}],"version-history":[{"count":2,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/8960\/revisions"}],"predecessor-version":[{"id":24613,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/posts\/8960\/revisions\/24613"}],"wp:attachment":[{"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/media?parent=8960"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/categories?post=8960"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nuxx.net\/blog\/wp-json\/wp\/v2\/tags?post=8960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nkatester 23802 94.4 0.1 3184 2520 ?? R Wed01PM 1582:07.71 perl udp.pl irc.world-crew.net 6667 1200 (perl5.8.8)<\/tt><\/p>\n
\n PID TT STAT TIME COMMAND
\n17603 ?? Z 0:00.01 <defunct>
\n17605 ?? S 0:03.76 .\/bash
\n23800 ?? Z 0:00.00 <defunct>
\n51838 ?? I 7:27.67 \/usr\/local\/bin\/php-cgi
\n51842 ?? I 7:17.46 \/usr\/local\/bin\/php-cgi
\n51843 ?? I 7:29.32 \/usr\/local\/bin\/php-cgi
\n51851 ?? I 7:19.06 \/usr\/local\/bin\/php-cgi
\n59959 ?? Is 0:00.93 \/usr\/local\/bin\/php-cgi
\n67261 ?? I 6:31.64 \/usr\/local\/bin\/php-cgi<\/tt><\/p>\n
\n142.166.3.123 www.katester.net - [05\/Sep\/2007:08:27:11 -0400] \"GET \/blog\/index.php\/feed\/ HTTP\/1.1\" 200 17637 \"-\" \"Jakarta Commons-HttpClient\/3.1-beta1\"<\/tt><\/p>\n
\n· The exploit was able to write a small script to the machine and execute it.
\n· This script then grabbed, spawned, and deleted udp.pl<\/tt>.
\n· I found things and cleaned them up.<\/p>\n