Spam Trojan pwnage, play-by-play
Its important to do as much evaluation as possible after an incident. This not only sheds light on how you were pwned, but it also provides invaluable lessons on how not to be pwned by the same bug in the future.
To wit; one of our partner laptops was recently compromised by a spamming trojan, despite having best-in-class HIPS and antivirus (best-in-class AV isn’t saying much when the bar is so low anyway. Oh how I love to hate the current state of AV technology!).
The trojan came from a website on 12/16 while the user was at home and thus not behind one of the enterprise IPS appliances. The user visited a malicious website somewhere and Internet Explorer created the file ‘C:\WINDOWS\system32\~.exe’.
Then the file ‘C:\Temp\AEVEm.exe’ contacted a website in Russia (75.126.154.90), presumably to check in and report its existence. Then it created the directory ‘C:\WINDOWS\system32\AppCert\’ and the following files therein; wsil32.dll and wnl32.dll.
The file ‘C:\Temp\AEVEv.exe’, then wrote to boot.ini and then created the file ‘C:\WINDOWS\system32\rpcc.exe’.
Then Internet Explorer renamed two files to: ‘C:\WINDOWS\system32\confmspt.dll’ and ‘C:\WINDOWS\system32\d3d8o.dll’. We don’t have records of what the original file names were.
After renaming two files, it looks like the machine rebooted. After the reboot, explorer.exe started attempting to send emails to Mother Russia (194.67.23.111). The HIPS firewall blocked the SMTP traffic. There were a few more reboots that day, followed by email attempts and one attempt by Outlook.exe to access ipconfig.exe.
The machine then fell into a rhythm of attempting to send emails using the following processes:
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\explorer.exe
C:\Program Files\Internet Explorer\iexplore.exe
There is no record of what created the AVEVEm.exe and AVEVEv.exe files.
Our AV didn’t detect any part of the trojan and the trojan was able to disable AV by blanking a registry key on start-up. I still haven’t found how its doing this, as the HIPS software protects the key. It must be doing it before the HIPS software is initialized.
We ran a couple of different anti-spyware programs on the machine and CounterSpy from Sunbelt was the only one that detected ~.exe as malicious. I’m waiting with baited breath for Sunbelt to release the VIPRE stand-alone AV…
The laptop belongs to a partner and he doesn’t want it rebuilt despite our advice to nuke from orbit, so we have no choice but to try to find all the droppings the trojan left behind. The fact that it’s able to disable our AV without the HIPS even detecting it is worrisome…
Stay tuned. We still have a lot of unanswered questions.
