Morris Worm: First Major Internet Worm
2 November 1988CybersecurityMajor incidentDate precision, exactEvidence grade, primary2 primary sources
Drivers:
The worm was not malicious in intent but exposed fundamental weaknesses in internet architecture and Unix security. The incident forced the community to acknowledge security as a critical concern.
In 1988, a university student accidentally caused the first major internet security crisis. He wrote a program that was supposed to quietly count computers on the internet, but a bug made it copy itself too aggressively, overwhelming and crashing about 6,000 computers. This was a wake-up call that the internet needed better security.
Morris Worm: First Major Internet Worm event plate
Structured atlas record showing date, domain, evidence grade, source count, and predecessor and successor links.
Forecasts and counterfactuals stay labelled as opinion in the event data. Source: Computer History Museum.
Before
The internet was a trusted academic network with minimal security. Systems assumed good faith from network users. There was no coordinated incident response capability. Security was an afterthought in most Unix systems.
What changed
Robert Tappan Morris, a Cornell graduate student, released a self-replicating worm that infected an estimated 6,000 Unix machines (10% of the internet). The worm exploited vulnerabilities in sendmail, fingerd, and rsh. It demonstrated that the internet was vulnerable to widespread automated attacks.
How it happened
Morris created the worm ostensibly to gauge the size of the internet. A bug in the reinfection check caused it to spread uncontrollably, overloading machines. The worm was released from MIT on 2 November 1988. Within hours, it had spread across the country. Administrators scrambled to disconnect systems and develop patches.
Outcomes
- Led to creation of CERT/CC (first incident response team)
- Raised awareness of internet security vulnerabilities
- First conviction under Computer Fraud and Abuse Act
- Catalysed development of security tools and practices
Limitations
- Incident response was ad hoc and uncoordinated
- No existing frameworks for handling such events
- Legal consequences unclear until prosecution
- Many organisations learned of vulnerabilities only after infection
Lessons learnt
- Trusted networks are not inherently secure
- Coordinated incident response is essential
- Software vulnerabilities can have widespread impact
- Even well-intentioned code can cause harm
Stakeholders and artefacts
Organisations
- Cornell UniversityacademiaMorris was graduate student
- MITacademiaWorm released from MIT systems
- DARPAgovernmentFunded creation of CERT/CC in response
Individuals
- Robert Tappan MorrisCreator, Cornell UniversityCreated and released the Morris Worm
- Eugene SpaffordAnalyst, Purdue UniversityPublished authoritative analysis of the worm
Artefacts
- Morris WormsoftwareSelf-replicating program exploiting Unix vulnerabilities
- CERT/CCmethodologyComputer Emergency Response Team created in response
Key terms
Causality
Preceded by: First ARPANET Message Transmitted.
Made possible: NIST Cybersecurity Framework Published.
On this course
Read in the path Cybersecurity: Threats and Defences.