Conficker Continues to Impact Networks

Published: 2009-09-25
Last Updated: 2009-09-25 21:39:11 UTC
by Deborah Hale (Version: 1)
2 comment(s)


It appears that Conficker is still alive and well.

I heard about a local company today who on Monday of this week started having some pretty strange goings on in their network and called in their consultants to try to figure out what was happening.  It turns out after much time spent trying to determine what was going, it was "just another Conficker Outbreak".   (Still working on it as a matter of fact). They do have anti virus however the infection went undetected for quite some time.  Why?  Because Conficker did what Conficker does and it over rode the security software and antivirus software to allow them to do their dastardly deeds while remaining undetected.  This company has close to 100 computers and more than 50% of them have been infected, some for a while it seems.  Conficker has continued to grow its little Botnet and the BotHerder is still spreading their damage.  If you look at the "pictorial" representation of the spread in the US alone from January to July it is pretty amazing.

We also received an email today from a reader whose company was experiencing Conficker activity.  So perhaps there is a new wave of the bad guy coming.  So just a reminder - quick check -

If this Eye Chart doesn't display the logo's for 6 of the top security sites in the world, you may be infected and will be the next to fall to the plight of the Conficker Worm.


Deb Hale Long Lines, LLC

2 comment(s)


You can see the current infection tracking stats and charts as gathered by the Conficker Working Group on this page:

As of yesterday, there are still over 6 million unique IPs seen for the A+B+C variants.
The network that I manage got hit by the conficker b/c variant this week. It seemed to start on 9/18. We run a mid-size network 1000 workstations and about 80 servers. We recently merged with another company and were unifying our anti-virus servers. During this process some PC's did not have antivirus protection and went unnoticed. We currently do not utilize any NAC/NAP services but are now looking into this. One tool that helped me to detected conficker was NMAP. It supports scanning your network for likely infected hosts. However, it did seem to break network shares to some of our fileservers. On these systems, the browser and server service needed to be restarted. Does anyone have any tips and tricks for conficker scanning using NMAP? What other tools, IDS/IPS do you guys and girls use to detect and prevent conficker?

Diary Archives