Morris Worm: when copying became the outage
PERIOD
1988; appeal 1991
EDITION
Short field file
REVIEWED
2026-11-19
The short version
On November 2, 1988, a worm began spreading between susceptible Unix computers. Copies attempted to reach more machines, while repeated execution consumed resources. A computer did not need its files erased to become unusable. The disruption was an availability problem.
What let it in?
MIT’s technical account describes several routes: a sendmail debugging feature, a fingerd buffer overflow, credentials, and trusted-host relationships. These were alternatives with different prerequisites—not four steps every victim followed. The fingerd exploit described by the researchers worked against a particular VAX environment, not every Unix machine.
The number needs a footnote
The FBI’s retrospective gives an estimate of 6,000 affected computers. GAO’s contemporary report says no official infection estimate existed. It describes the 6,000 figure as an extrapolation and records a competing estimate of 1,000–3,000. Those figures are not a verified census. Infected computers and people affected by disrupted services are also different populations.
From the workbench
A machine can stop doing useful work without losing a single document. My takeaway: when investigating an outage, ask what is consuming the resources as well as what files changed. That is an analytical lesson, not a claim that one symptom proves a worm.
What this file leaves open
The exact launch chronology, a complete infection count, and an explanation of the author’s overall motives are outside this short account. It does not offer a psychological diagnosis or a definitive damage total.
