We've written about McColo hosting the Srizbi Command and Control servers a couple times, but today I saw a fun wrinkle that I haven't seen before.
After my machine got infected, it went through the standard connectivity test. The first test was the standard "can I send SPAM?" test that Bots do - ie, the outbound port 25 check. However, when I took a closer look at the SPAM test, the test domain is also hosted by McColo!
Above you see Srizbi sending a blank message to [blocked]@bestyounggirls.com, and the IP it relayed it through was 188.8.131.52. A quick 'dig' of bestyounggirls.com (NSFW) shows that it also resolves to 184.108.40.206. The explaination is that Srizbi wanted to see if the Botted machine had the ability to send SPAM, so it sent a SPAM message to a domain that was controlled by the group who runs the Botnet. If the Botted machine was not able to send SPAM, there's no need for it to try and possibly be detected by the systems administrator of its network.
After it does the SPAM test, you can see the normal Srizbi communication, again, on a different McColo IP (I altered the headers to take away identifyable information)
POST /r/A1412B-12F1E6-A55215 HTTP/1.1
After the POST (and the Bot sends up a couple hundred K of data), it does a GET and exchanges more data
GET /g/A9123B-98F13R1-A011N12 HTTP/1.1
A quick google shows very little information for 220.127.116.11, despite the fact that it is hard coded into Srizbi. No "fast flux" in use here! The last interesting wrinkle about this is that it is communicating over both UDP and TCP on port 18923.
Alex Lanstein @ FireEye Malware Intelligence Labs
Comments/Questions to email@example.com