A scheduled denial of service attack against Microsoft Corp.’s main software update Web site did not materialize Saturday, as computers infected with the W32.Blaster worm failed to find their target.
Blaster first appeared on Monday and quickly spread to computers worldwide by exploiting a known security vulnerability in Microsoft’s Windows operating system.
By Friday, the worm, which targets a Windows component for handling RPC (Remote Procedure Call) protocol traffic called the Distributed Component Object Model (DCOM) interface, spread to more than 423,000 systems, according to Oliver Friedrichs of Symantec Corp.
In addition to infecting vulnerable Windows machines, Blaster worm was programmed to launch a denial of service (DoS) attack against windowsupdate.com, an Internet domain owned by Microsoft and used to distribute software updates to Windows customers beginning on Saturday.
However, an error in Blaster’s design combined with last minute actions by Microsoft to change the registration of windowsupdate.com cut short that attack.
Blaster’s author provided the incorrect domain address for windowsupdate. The address specified in the worm’s code, windowsupdate.com, simply forwards users to the actual Windows update site, windowsupdate.microsoft.com, according to Mikko Hyppönen, head of antivirus research at F-Secure Corp. in Helsinki.
On Thursday, Microsoft delisted the windowsupdate.com domain name, calling it a “nonessential address.” That solution also removed the threat of collateral damage from the attack, because requests for windowsupdate.com would never leave infected machines, slowing down the Internet, according to Sean Sundwall, a Microsoft spokesman.
On Saturday, Microsoft didn’t detect any irregular network activity associated with the Blaster worm, Sundwall said.
The SANS Institute Inc.’s Internet Storm Center reported Saturday that the DoS attack anticipated from Blaster had been avoided.
The number of Blaster infections is also down more than 80 percent since the worm’s peak on Monday, indicating that vulnerable computers are being cleaned and patched by their owners, Friedrichs said. Symantec expects that trend to continue, he said.
In time, Blaster will join predecessors like the Code Red and NIMDA worms, inhabiting a small population of infected machines that pose a risk to new, unpatched systems, but not spreading much beyond that, he said.
For Microsoft, the Blaster worm outbreak stoked internal efforts to shore up vulnerable services. Even though Blaster missed its target, future worms might be smarter, faster and more destructive, Friedrichs said.
Microsoft is using the occasion to take “a number of steps” to protect valuable customer services such as the windowsupdate.microsoft.com Web site from attack, Sundwall said. He declined to provide details of what changes the company is making.
Microsoft is also using the Blaster outbreak as an impetus to improve communication with consumers about the need to patch regularly, Sundwall said.
“We learn from every worm out there. What we learned from (Blaster) is that there aren’t enough consumers who installed the patch and use (Windows) autoupdate,” he said.
Microsoft customers should expect a concerted effort by the Redmond, Washington company to reach out in coming weeks and raise awareness of the need to patch vulnerable systems, he said.