IT Security Blog

23 June 2009

Brief Storm/Waledac Timeline and Its Relationship with Conficker


The folks over at Cisco posted a very interesting blog writeup about the Storm/Waledac botnets and how their marriage to Conficker was consummated in order to start monetizing the enormous computing power of the Conficker botnet. 

What I found most interesting was the part about how Conficker would hook itself between Wireshark and the network driver (likely within the winpcap library) to hide all of the network interfaces from Wireshark, essentially rendering the packet sniffing tool useless.

Looking ahead, this makes me wonder what else malware could do to alter the behavior and functionality of other tools that security researchers use to analyze malware.  We've already seen Conficker introduce signed, encrypted updates to keep researchers from analyzing updates and penetrating its network.  This development of malware physically altering how analysis tools work could be a significant game changer in the cat and mouse game of being able to reverse engineer malicious code.  This is definitely something that warrants continued monitoring to see if this tactic continues to be employed by cyber criminals, or improved upon.
Posted by smasiello at 4:35 PM | Link | 0 comments

No comments found.

Commenting has been disabled for this entry.