Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A computer worm is a type of malware that replicates itself and spreads automatically from one system to another across a network, without needing a host file or any user action.

What Is a Computer Worm?
A computer worm is a type of malware that copies itself and spreads from system to system on its own. Once it infects one machine, it scans for other vulnerable systems and infects them too, then repeats the cycle. Unlike a virus, a worm does not need to attach itself to another file, and it does not wait for anyone to open anything. That independence is what allows worms to spread at extraordinary speed.
Some worms simply spread. Others carry a payload, such as ransomware, a backdoor, or code that destroys data, which turns a fast-moving infection into a major incident.
Worms use several propagation methods, often in combination:
| Year | Worm | Impact |
|---|---|---|
| 1988 | Morris worm | Infected an estimated 6,000 machines, about 10% of the internet at the time |
| 2000 | ILOVEYOU | Spread through email attachments to tens of millions of users worldwide |
| 2003 | SQL Slammer | Infected around 75,000 servers within ten minutes, doubling roughly every 8.5 seconds |
| 2008 | Conficker | Infected millions of Windows computers and lingered for years |
| 2010 | Stuxnet | Spread via USB drives and networks to sabotage industrial controllers in Iran |
| 2016 | Mirai | Built a huge botnet from IoT devices using default passwords |
| 2017 | WannaCry | Combined a worm with ransomware, affecting around 150 countries, including parts of the NHS |
| 2017 | NotPetya | Destructive worm disguised as ransomware, causing billions in global damage |
WannaCry and NotPetya both used EternalBlue, an exploit for a vulnerability in Microsoft’s SMBv1 protocol. Microsoft had released a patch (MS17-010) in March 2017, two months before WannaCry struck, which shows how closely worm outbreaks are tied to patching gaps.
Speed is the defining threat. Human response processes, such as raising a ticket, assessing the risk, and scheduling a change, cannot keep up with an infection that doubles every few seconds or minutes. By the time an analyst notices, thousands of machines may already be affected. Worms also spread indiscriminately, so organisations that were never deliberately targeted can become collateral damage, as many did during NotPetya.
Because response is often too slow, defence relies mainly on architecture and preparation:
Classic mass-spreading worms are less common than in the early 2000s, partly because operating systems are better protected and attackers prefer quieter, targeted intrusions. However, worm-like behaviour remains common. Ransomware groups use automated propagation inside victim networks, IoT botnets continue to spread through default credentials, and any newly disclosed, remotely exploitable vulnerability in a widely used service carries the risk of a new worm.
At Privia Security, our Network Security Services test how far an automated infection could spread through your network, and which segmentation and hardening measures would contain it.
A virus attaches itself to a host file and spreads when that file is opened or run, so it depends on user action. A worm is self-contained and spreads automatically across networks by exploiting vulnerabilities or weak credentials, with no user involvement. This independence makes worms capable of spreading much faster than viruses.
It is much harder, but still possible. Some worms spread using weak or stolen credentials, default passwords, or zero-day vulnerabilities rather than missing patches. Patching removes the most common route, and combining it with strong unique passwords, segmentation, host firewalls, and endpoint protection greatly reduces the remaining risk.
Isolate affected network segments quickly, block the protocol or port the worm uses at internal firewalls, and use endpoint tools to contain infected hosts. Then patch or mitigate the vulnerability, reset compromised credentials, and restore affected systems from clean backups. Having segmentation and an incident response plan in place beforehand makes containment far faster.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.