My team is working on info for this, but it looks like all the major Anti-Virus companies have fixes for this (Symantec, McAfee, etc.)

Also this link might help as well: http://windowssecrets.com/2009/03/30...before-April-1
[Reply]

Good post.


More useful info (including removal tools) here:

http://www.iss.net/threats/conficker.html
[Reply]

Thanks Andrew
[Reply]

You are welcome. :-)


Over here it is so far so good. We have close to 150 machines...knock on wood.
[Reply]

And for the record - the link is NOT a rickroll (for April Fool's sake) :-)
[Reply]

As much hype as this has received, I'm looking at it like y2k all over again.

200 some odd desktops here and 25-30 servers..... all is well.
[Reply]

What does it do?
[Reply]

I think it flicks con?

No one knows. That is why it is a buncha BS hype. There are dangerous virii out there every day, this one is just being associated with April fools day so the media is having a field day.

All my opinion, of course.
[Reply]

Was the virus going to do something today?
[Reply]

Like Stu said, no one really knows. But when you consider how large of a botnet it is (something like 8% of all the PCs in the world) there is some reason for concern. Really it is only going to affect far out of date systems.

If I understand it correctly today was the day that it was supposedly going to start recieving messages from those that control the botnet. Again, no one really knows.
[Reply]

So it was just sitting in the weeds waiting for a command. Usually viruses already have commands when sent out.
[Reply]

Or as someone pointed out - it might be a big April Fools Day joke...but better safe than sorry as far as I am concerned (especially with 20,000+ computers not counting servers)

Have a cigar and some popcorn - and wait and see what happens :-)
[Reply]

I thought it bombed the hell out of you anonymously. I had that virus a week or so ago. :-)
[Reply]

Yes you did!! :-):-):-)
[Reply]

850 servers, 15-20,000 PCs and no word of an outbreak. I'm pretty sure the Zero day patch Microsoft released in October prevented this vulnerability. I pulled an 18 hour day back then to make sure all 800+ servers were patched. Made it home at about 6AM the next day.
[Reply]