The Conficker worm may have already created havoc with the estimated nine million PCs it's infected, but one security expert warns the worm is only dormant, perhaps to be unleashed at a later date with an even greater vengeance.
Jason Miller, manager of security and data at US security technology vendor Shavlik Technologies, says Conficker (also referred to as Downadup) may well be undergoing a test run, during which its makers are learning of what works best.
If that's the case, there's a more malicious version in store for everyone, predicts Miller. "It's a blessing in disguise," he says, and organisations and individual users can take advantage of this lull to ensure their systems are secure. "This worm is not going to go away."
Nor does Miller think the estimate of infected PCs at nine million by Finland-based security firm F-Secure is a mere scare tactic. "Whoever wrote this virus has a lot of information tucked in their head," he says, referring to the sophisticated techniques employed by Conficker.
There's a complexity with this one, says Miller, that's replacing a virus or worm's usual one-dimensional approach, which is either to set up spam or download an application on a victim PC. Upon closer inspection, Conficker assumes a multi-vector strategy employing brand new techniques not previously seen "and they're pretty scary," he says.
Among those, the worm takes advantage of a previous file-sharing vulnerability in Microsoft Windows Server, and also proliferates itself by infecting USB devices.
Users of Windows 2000, Windows XP and Windows Server 2003 systems are most at risk, according to Microsoft, which last October released a patch, MS08-067, intended to protect systems from Downadup, and has also advised users to download the Malicious Software Removal Tool (MSRT), updated last week to detect and remove the worm.
Organisations should scour their network for all physical and virtual machines that exist, such as the one "buried in the basement somewhere," says Miller. "Look for those systems that you can't find. Don't worry about the main PCs and the servers on the floor. All it takes is one."
Miller also suggests stopping Downadup by disabling ports 135 and 443. However, he cautions, that is a band-aid approach that risks interrupting file-sharing, thereby disrupting the internal functioning of Windows and other systems that rely on those ports. "If you have to and you're in a crunch, I would say do it, but just be advised it will break functionality of products," he says.
Hardening passwords and enforcing policies for password creation, says Miller, is recommended, so "you can't let me have my password as 'Miller' when my username is 'Jason.'"