The Apology Could Not Get Through

1. A connected network

In November 1988, the internet linked universities and research organisations. A self-propagating programme released from MIT began spreading across that network. Connected computers allowed a program to travel beyond its starting point. That reach made unintended behavior capable of producing widespread disruption.

The connections were about to carry the wrong kind of collaboration.

2. A network carries the consequence

Software released onto connected machines can produce effects far beyond the computer where it begins. Each additional host can change the scale of the incident. The worm's spread therefore turned a program's internal behavior into a shared operational problem, linking administrators who might otherwise have been dealing only with their own systems.

The mistake had found a transport network.

3. Systems slow down

The worm consumed resources and disrupted computers. An estimated six thousand machines were affected within a day, a substantial share of the network then. A mechanism intended to keep the program present also multiplied its impact. Technical choices inside the code affected machines elsewhere.

The new arrival was making itself impossible to ignore.

4. A removal message

Its author sought to send an anonymous apology and removal advice through a friend. The disrupted network hindered the message’s timely delivery. Network access created both an opportunity to spread and a route for response. Administrators needed to understand the behavior while their systems were affected.

The repair instructions had to travel through the damage.

5. The identification

Investigators identified Cornell graduate student Robert Tappan Morris as the author. A programme released at MIT did not establish that its creator belonged there. Restoring service required coordinated technical work. The episode exposed how a shared network could turn separate problems into a collective emergency.

The launch address had not been a reliable return address.

6. The response has to travel too

People restoring their computers needed information about behavior occurring elsewhere on the network. A coordinated technical response could help identify the program and reduce disruption. The episode exposed the same connection from both directions: the network helped the incident spread, while communication among its users became essential to understanding and containing it.

The shared problem required a shared repair.

7. The aftermath

The case produced a landmark computer-crime prosecution and heightened attention to network security. Connected systems required coordinated defence as well as connectivity. The legal case followed the consequences of the program's release. A stated intention did not remove responsibility for the actual damage.

The internet had learned how quickly one problem could become everyone’s.

Sources

• FBI — Morris worm