Not all of you folks on my FL read databeast, or keep up with the tech press. Which is why I’m quoting his most recent post in its entirety here:
Next week, at 8pm EST/00:00 GST, the Conficker worm will download its next code update.
I’ve spent the last 4 months spending damn near my every waking hour fighting this thing.
If you have no idea what I’m talking about, just go google ‘Conficker’ now. I’ll be happy to answer any questions.
In the meantime, go to http://windowsupdate.microsoft.com/ and download every last update on there.
Tell your friends to do the same.
if you can’t reach that site, you are already infected. Take your machine offline and get it disinfected by a professional.
But remember this, right now If you are not part of the solution, you are part of the problem.
Conficker is shaping up to be the scariest, largest botnet ever to have existed. If you use Windows as your operating system, and you don’t regularly update it, you are part of the problem, and your computer is likely now the property of some shadowy criminal syndicate based out of God-Knows-Where.
If you aren’t a Windows user, but you know people who are, tell them the above instructions. We have less than 7 days until what could, in the worst case scenario, be the most destructive event ever witnessed on the internet, a vast, data-stealing network owned by an organized crime syndicate. We aren’t talking science fiction here folks.
If every man would sweep his own doorstep the city would soon be clean.
Italian Proverb
He’s not kidding, folks. Conficker (aka Downup, Downadup, or Kido) is serious bad news. It’s the next level of Internet worm evolution; it’s Botnet 2.0, the most sophisticated worm yet seen. During one of its major activity spikes, on January 15-16, Conficker infected 1.1 million PCs in less than 24 hours. At that time, F-Secure estimated — conservatively — that 3.52 million systems were infected worldwide. By January 21 the number was believed to be around 9 million. Current estimates run as high as 12 million.
For the technically knowledgeable among you, SRI International has an analysis of the most recent Conficker-C variant here. For the non-technical, McAfee has some less technical information about what it does here. And PC World has an article here detailing how it attacks and some measures you can take to protect yourself if you’re not already infected. (The article is slightly out of date; one recent Microsoft security patch disables AutoRun for you as a precaution.)
One point from databeast‘s post cannot be emphasized enough:
If you run Windows, with ANY browser, and you can read this post, but you cannot get to www.windowsupdate.com, or GRIsoft.com (home of AVG antivirus), or Trend Micro, or Sophos, McAfee or Kaspersky or any other antivirus site, assume you are already infected. Take your computer offline and seek professional assistance to get it disinfected and patched.
On April 1, the Conficker botnet goes active. And we don’t have any idea what its new instructions will tell it to do. But it could be very, very bad.
UPDATE:
Since Conficker can’t block downloads of tools from sites that don’t match its internal list of strings, I’ve mirrored several of the free Conficker removal tools locally:
- Enigma Software’s Conficker removal tool
- BitDefender’s single-PC Conficker removal tool
- BitDefender’s Conficker removal tool for Microsoft networks
- F-Secure’s Conficker removal tool
- F-Secure standalone worm-detection scanner, less specific
So if you can’t get to windowsupdate or any of the antivirus sites, you can download removal tools here.
no subject
no subject
no subject
no subject
I ran a virus scan at the weekend too (quite by coincidence) and that was clean.
no subject
We recently switched from AVG to Avast!, because while we'd been very happy with AVG Free up to v7.5, AVG8 just really chowed down on the CPU. Avast! also updates more frequently — as much as several times a day — and does an initial post-install scan actually before Windows fully boots, which prevents a pre-existing infection from using certain Windows tricks to hide from the scan.
no subject
no subject
no subject
no subject
no subject
No wait, no I dont.
still, a vote for Avast! here, It's been my primary suggestion to people for the last two years now
no subject
Hrm...the timeline is a little off...
no subject
no subject
That joke's now entering 'Ha! Ha! Only Serious!' territory.
no subject
no subject
no subject
no subject
no subject
Our home "data server" is a Win98SP2 box sitting on the floor of the den, with only power and ethernet cables running to it. (No monitor, no keyboard, no mouse—everybody told me Windows would complain, but I haven't had any problems.) I can perform maintenance on it via RealVNC, but updating Windows and rebooting is sort of painful.
no subject
If by 'affected' you mean 'impacted by the effects of', then no computer is immune.
Do you allow a windows machine to access files on your mac? is that windows machine infected? If the situation we are predicting comes true, then come April 1st, all your data is up for sale for the highest bidder.
Users of alternate operating systems are safe if they have *no* interaction with windows machines.
no subject
no subject
Enjoy!
no subject
I am more disturbed that the "bad guys" now know how to make a significantly nastier worm. Once the proof of concept gets tried out, there are sure to be more of the same type of attack.
It is ugly that security has such a tangential role in most computer use. Nobody wants to pay for it. When a big problem (like Conficker) is alleviated by good publicity, we are accused of crying wolf. We can't win in the public or business executive's eye.
no subject
no subject
no subject
no subject
(im the CIRT engineer for RSA/EMC)
no subject
no subject
Fortunately the worst we ever got was a quickly-contained outbreak of an Excel macro virus that someone, probably the comptroller, brought in on a floppy disk from an unsecured home machine.
no subject
As far as passwords went, I just shut down some access to the business system for easily cracked passwords. I figured that everyone used the same password everywhere, so it was all good. (I was bad, I didn't require frequent password changes. I reasoned that a long-term, secure password was better than a short-term, weak password.)
[The Webmaster kept the M$ 13? ports open on his BSD web server. He got a laugh every day at the script kiddies trying to run IIS exploits against his system. Odd sense of humor...]
no subject
Heh. Been there, done that. :) I have most of the common PHP and CGI exploit URLs tarpitted. But I changed my incoming ssh port because I got sick and tired of my logs filling up with the same idiot script-kiddies blindly trying the same brute-force dictionary attacks day after day after day after day. There was one 'tard who would restart the dictionary attack every day at about the same time, from the same point in the dictionary. It stopped being funny, and became just pathetic and annoying.
no subject
Par usual, I doubt anyone will and I will then wonder why I bother, realising that Kantian Categorical Imperative thing runs deep with me and I post because that is who I am. '
Thanks and- as always- my respects.
no subject
I posted last night, and I have only seen one response -- someone I know stating that he thinks it's all just an April Fool's Day joke.
*sigh*
no subject
But if it weren't for fools, would we have half as many friends?
no subject
no subject
Joe Stewart, a senior researcher at SecureWorks, notes that the infected PCs are already capable of receiving directives from the controllers via the P2P network, "so the 50,000 domains aren't really needed. They could even be a practical joke on the part of the authors." (http://www.usatoday.com/money/industries/technology/2009-03-24-conficker-computer-worm_N.htm)
In other words, new marching orders and code updates can be pushed out to Conficker at any time, so why bother scheduling a pull on a particular date and time?
Regardless, it is always excellent advice to make sure that patches and AV software are up to date.
no subject
no subject
when the worm originally surfaced, it was the afternoon of the last workday before we all went on vacation for thanksgiving. The April 1st date is exactly because "The Diversionary attack you are ignoring is the primary assault"
no subject
no subject
This thing wasn't engineered- it is the biggest bodge job in the history of humanity. Yet it flys...
no subject
no subject
Patch your damned systems.
For some unknown reason...
Advice Please
Do I specifically boot Windows just to scan it, or can I leave it until after April 1, and do the scan then?
(I only ever use Windows for some specific school programs (over), or to play a couple of games (seldom, and never on the net.))
Re: Advice Please
The other side of the coin is, when you DO boot Windows, you should make sure getting Windows patched is the very first thing you do.
Your assumption that the ME box is safe is probably correct. ME is a completely different architecture and kernel, and it doesn't have the exploited service at all. Then again, it's also widely considered the worst version of Windows ever...
Re: Advice Please
Updating Windows is an issue. On some of the machines, it is demanding to install Windows Genuine Advantage before any other updates will be applied. I refuse to run WGA. It seems to get very unhappy if it can't find the internet. Usually, if I am in Windows, the internet is disabled for that machine. The whole OS leads me to cuss. It is not so much the UI or the way it runs programs, it is the ongoing cost (in time more than $$) to keep it running safe and secure[?]
no subject
But that's because the cable guy hasn't come yet to hook me up. The minute I'm live on Tuesday night, i'm going to update all my security stuff.