Slashdot Log In
Anti-Virus Bug Briefly Identified Windows Explorer as Malware
Posted by
Zonk
on Tuesday December 25, @11:23AM
from the err-oops-pay-no-attention-to-your-OS dept.
from the err-oops-pay-no-attention-to-your-OS dept.
SJ2000 writes "Windows Explorer was quarantined last week by Kaspersky Lab's antivirus software after being falsely identified as malicious code. The security company's systems had decided that a virus called Huhk-C was present in the explorer.exe file, leading to its confinement or, in some cases, deletion. The bug was only live in the wild for two hours, and ended up affecting just one corporate customer and a handful of home users."
Related Stories
Anti-Virus Bug Briefly Identified Windows Explorer as Malware
|
Log In/Create an Account
| Top
| 131 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

I don't get it... (Score:5, Funny)
Re:I don't get it... (Score:5, Funny)
Because it only identified the explorer component.
Re:I don't get it... (Score:5, Funny)
Re:I don't get it... (Score:4, Funny)
maybe that's why I got laid off...
Where is the Obligatory Gay Male Coprophilia Porn (Score:4, Funny)
I guess it's just too early still in Seattle... Maybe they will post it later.
Merry Christmas Bill!
Obligatory fixed (Score:4, Funny)
Windows Is Not A Virus! (Score:5, Funny)
jk (Score:4, Funny)
um, don't they test these things before releasing? (Score:5, Insightful)
That's my first reaction, now I'm off to RTFA
Re:um, don't they test these things before releasi (Score:5, Funny)
Oh, you mean Kaspersky Labs
O rly? (Score:5, Funny)
And yet it still made the front page of Slashdot.
Re:O rly? (Score:5, Insightful)
So what does that make people who are stupid enough to mistake Internet Explorer for Windows Explorer?
Random Thought (Score:1)
Have you even used windows lately? (Score:3, Funny)
It's not a virus, sure. Viruses tend to mature, become more efficient...
But Explorer sure feels like malicious code...
Dumb article (Score:2, Funny)
As Windows Explorer is the graphical user interface for Windows' file system, this made it difficult to perform many common tasks within the operating system, such as finding files.
Gee, makes it sound like losing explorer.exe is only mildly inconvenient.
AND???? (Score:1)
What's funny is, if I saw that explorer was missing on my system, by the time I reloaded the OS (cause *obviously* it's infected/broken/normal operating procedure), I never would've known the cause. It was pulled by the time I would've finished installing.
Of course, then I'd have to go and find my Gentoo CD so I could reload GRUB. That would've been more painful than the rest of the OS reload that I expect to do every six months anyway.
Slow news day (Score:2)
Seen it all before... (Score:3, Interesting)
We've also had Norton 'false positive' on the Windows version of Oolite.
One of these days, a widely used, automatically updated virus scanner is going to detect something like KERNEL32 as malware and kill a whole lot of machines. Wasn't there a problem like this with the Chinese version of Windows earlier this year?
HUHK = Hamburger University of Hong King (Score:3, Funny)
Anti-Virus Bug Briefly Identified Windows Explorer (Score:2, Funny)
Re:Anti-Virus Bug Briefly Identified Windows Explo (Score:5, Funny)
No Mistake (Score:1)
Correction (Score:1, Redundant)
Handful of consumers? (Score:1)
Why things like this happen (Score:5, Insightful)
But how? Don't they test?
Of course they do. AV developers usually have some way to test against the most common software (and a few more software packages) before issuing a new signature. Though, as you can hopefully imagine, that takes time. The "whitelist" box that contains those "known good" files contains literally gigabytes (and soon terabytes) of software. As you can imagine, it takes a LOT of time to scan it all.
Time, though, is of the essence in the malware fight. You NEED that signature out before the proverbial shit hits the fan (i.e. before your customer opens that infected spam mail that was just distributed a few billion times globally). So your sig update has to go out NOW. Preferably it should've been out an hour ago.
How do you solve that quandary?
There are a few strategies. But they all come down to one single problem: Having a current version of every file you want to whitelist. So what most likely happened is this:
MS pushed an update for the file in question, most likely another of their infamous "silent" updates. You know, the ones you don't even notice. Now, if it wasn't a "silent" one, then one should wonder whether Kaspersky was sleeping (because they didn't fit it into their whitelist box in time) or whether it was pushed JUST at that time when they committed that update. Unfortunately such coincidences do happen.
Now, I'm not working at Kaspersky. Rather, I'm working at one of their fiercest competitors. So I should probably rejoice at their blunder (and I'm fairly sure my boss will be in a GOOD mood on Thu, time to ask for a raise, I guess). But it can, did, does and will happen. To anyone in the biz. No matter how good you are and how good your false positive alarms and nets are, it can happen to everyone. If anything, this proves it. Kaspersky IS one of the key players in the business, and they usually know what they're doing.
That's one of the reasons why I do highly recommend that you set your AV tools on "ask me before any action" mode. Yes, it bugs you every now and then, but it also means that things like this won't happen to you should your AV tool manufacturer have a similar problem one day.
Thats funny (Score:2)
If Language is a Virus.. (Score:1)
oops. shh, don't want to give the government any more ideas here..
Pre-emptive paranoia (Score:1)
"Just a handful" of home users (Score:1)
Without any information about the "virus detection" at the time, I took the only safe path I could...
Doing a full backup and reinstalling Windows and Linux. Wasted an entire day, thanks kasperkey
I just had to repair a system this happened to (Score:1)
This isn't all of it (Score:2)
First, back on the 14th, they screwed up and issued update that had SERIOUS consequences for quite a few people running large networks. One guy had 700 machines down. Turns out they had a bug in the code since 1996, which was only discovered when they switched Microsoft compilers for version 7. The Linux compilers caught the bug and so the Linux version of KAV didn't have a problem. But the Microsoft compilers compiled the bug with no warnings or error messages, so it slipped through. At least that was the explanation Eugene Kaspersky put out on the forum.
Second, this latest bug with Explorer which was fortunately caught within a couple hours. My client's machines never even saw it because their update cycle was longer.
I've just started installing KAV 6.0 on one of my client's machines. He was suspicious of using a Russian company in the first place, but I told him it was okay since they're a high detector, got a management kit, good price for his 24 machine, etc.
Then this shit happened. Doesn't make me look good, either. Fortunately it didn't drop our machines, it just caused a message to pop up saying the application launch didn't work.
And recovering has not been easy, since the Admin Kit apparently still has the crap in it's source directory used for installing KAV on client machines. I'm going to have to uninstall and reinstall the Kit to make sure the buggy components are not there as I finish installing the rest of the machines.
But what someone else above said is likely true - sooner or later some AV is going to drop thousands of scores of thousands of machines. This is obviously true when you consider that AVs are programs that burrow deep into the OS AND have almost continual updates of both signatures and software components. It's like running Windows Update every hour of every day! Sooner or later there's going to be a catastrophe. It's just not a sustainable process.
Re:windows? a virus? no wai (Score:1, Redundant)
Re:bug? (Score:1)