Bandwidth Eating, Blacklist Causing Zombies Oh My!
Posted by deneb on 18 Jan 2009 | Tagged as: Computers and Technology, Security, The Caffeinated Duck, Windows
A couple of weeks ago, I received an email saying that we are spamming. One of our IP addresses was listed, which unfortunately was our NAT (PAT for you purists). “OK,” I thought, “7 schools and our district office that’s about … 1000 computers, and one or more of them are spamming. Ugh!”
We’re still in the process of migrating from Netware 4 & 5 to Windows 2003. Much of the IP address allocation and computer naming was done long before I arrived. Finding the IP addresses of the offending computers was not really difficult. Between the firewall and the LAN, run wireshark which can examine all traffic coming and going from the network. You need to make sure that your analyzer PC is attached to a hub and not a switch on this link, otherwise it will not see packets that are not destined for itself.
Run Wireshark and filter for smtp traffic (port 25). Let it run for 5 minutes or so. The results will show your email server traffic (if you have one) and any traffic generated by a client bound for another email server. Be aware that not all traffic coming from port 25 on clients necessarly means it is a spam zombie - they may be using their ISP’s mail on their work computer or something of the like. It is an excessive amount of traffic on port 25 going to several different mail servers. You can also examine the packets, strange email addresses are also a tipoff.
At this point, I located 2 computers generating what would amount to several hundred emails per hour. Since they were not computers that have been upgraded yet, I only knew what school which they were located. As we bring clients on to the new server, they get renamed with the school and room number (i.e. at Dalton James Elementary School, room 116 which is a lab, 4th computer would be named DJES116LAB04) but these computers had the default manufacture name and number as the computername - which I got from DHCP (since there is no local DNS or WINS). I assigned these computers a DHCP reservation so they wouldn’t get a different IP address before I could find them, and then blocked them at the PIX (firewall). This keeps them from sending spam, plus often the user would come looking for us when their computer all the sudden cannot get to the internet. It took one of our savvy tech who knew that school just a few minutes to find the computers, and we pulled them off the network and reimaged them.



