Top Reasons Why The Conficker Worm May Strike Back
The Conficker worm affected users nearly one year ago. But now that it has left the headlines, there might be a false sense of security in the Windows ecosystem
It was just under a year ago that the Conficker worm was first detected. It was ravaging Windows PCs all over the world. The worm exploits Windows flaws to link the host computer to virtual command that can be controlled by the worm’s remote authors. Conficker still controls millions of computers all over the world.
But as Conficker fell from the headlines, many of us forgot about its potential danger. And in the course of a year, not much has been done to ensure that a major breakout of Conficker or something similar won’t happen again. Simply put, the threat is still there and, unfortunately, it can impact users once again.
Here’s why:
1. Security is a “catch-up” game
Unfortunately, operating system security isn’t proactive. In most cases, an issue erupts and the security community scrambles to fix it. That happened with Conficker. And since the worm is still impacting the globe, there’s little chance that it won’t continue to happen. We need to catch up to the malicious hackers.
2. Blame the users too
Users don’t spend enough time focusing on their own security. Conficker was able to infect so many computers because users just don’t know how to handle security issues when they arise. It gets worse when Microsoft releases a security patch for Conficker and a large portion of its users (30 percent, according to most estimates) don’t even patch their systems. Until users understand the security ramifications of their actions, Conficker can very easily happen again.
3. Malicious hackers are becoming more sophisticated
Since Microsoft and security firms are doing a better job of combating security issues, malicious hackers are becoming more sophisticated. Nowhere is that more evident than in Conficker. It wasn’t a simple Trojan or virus. It was designed specifically to capitalise on the weaknesses inherent in Windows—users and code. It was a sophisticated attack. And so far, the security community is having a hard time combating it.
