The Sapphire Worm was the fastest computer worm in history. As it began spreading throughout the Internet, it doubled in size every 8.5 seconds. It infected more than 90 percent of vulnerable hosts within 10 minutes.

The worm (also called Slammer) began to infect hosts slightly before 05:30 UTC on Saturday, January 25. Sapphire exploited a buffer overflow vulnerability in computers on the Internet running Microsoft's SQL Server or MSDE 2000 (Microsoft SQL Server Desktop Engine). This weakness in an underlying indexing service was discovered in July 2002; Microsoft released a patch for the vulnerability before it was announced. The worm infected at least 75,000 hosts, perhaps considerably more, and caused network outages and such unforeseen consequences as canceled airline flights, interference with elections, and ATM failures. Several disassembled versions of the source code of the worm are available.

Propagation speed was Sapphire's novel feature: in the first minute, the infected population doubled i n size every 8.5 (±1) seconds. The worm achieved its full scanning rate (over 55 million scans per second) after approximately three minutes, after which the rate of growth slowed down somewhat because s ignificant portions of the network did not have enough bandwidth to allow it to operate unhindered. Most vulnerable machines were infected within 10-minutes of the worm's release. Although worms with this rapid propagation had been predicted on theoretical grounds, the spread of Sapphire provides the first real in cident demonstrating the capabilities of a high-speed worm. By comparison, it was two orders magnitude fa ster than the Code Red worm, which infected over 359,000 hosts on July 19th, 2001. In comparison, the Cod e Red worm population had a leisurely doubling time of about 37 minutes.

While Sapphire did not contain a malicious payload, it caused considerable harm simply by overloading net works and taking database servers out of operation. Many individual sites lost connectivity as their acce ss bandwidth was saturated by local copies of the worm and there were several reports of Internet backbon e disruption (although most backbone providers appear to have remained stable throughout the epidemic). I t is important to realize that if the worm had carried a malicious payload, had attacked a more widesprea d vulnerability, or had targeted a more popular service, the effects would likely have been far more seve re.

This document is a preliminary analysis of the Sapphire worm, principally focused on determining the spee d and scope of its spread and the mechanisms that were used to achieve this result.