recommended reading

How Computer Viruses Get Their Names


Heartbleed, Melissa, Klez, Nimda, and Sasser. All of these innocent sounding words could ruin your computer, steal your information and impact your digital life forever. These computer viruses and system vulnerabilities are the best at what they do: breaking stuff. But how did these terrors get their names? 

There is not one standardized way to name a viruses. These aren't hurricanes, there's no master list to turn to, and no authority that watches over them to regulate how their dealt with. Instead, there are three main avenues for virus naming: when the name is given to the virus as part of its programming; when the vector by which the virus is spread determines the name; and when a vulnerability is found and then named after the fact, usually by its discoverer.

Historically, back when viruses got around mainly through the forwarding of emails, the name of the threat would be based on the file name of the attachment. One of the worst viruses ever seen was called "ILOVEYOU." It spread like wildfire because of the pleasant sounding email subject and attachment (Love-letter-for-you.txt) The happy attachment turned out to be malicious code that overwrote existing files with copies of itself. 

Koobface and Vundo were named after the method by which they were spread. Koobface, an anagram of Facebook, was a worm that spread through the social media site. Vundo was a combination of Virtual and Mundo ("world" in Spanish), and it spread through virtual communities. 

Then, there are vulnerabilities like Heartbleed. Heartbleed was a bug found in the OpenSSL encryption service. The line of code that contained the glitch was CVE-2014-0160 — not exactly the most memorable name. Ossi Herrala, a system administrator at Codenomicon (the company which found the bug) came up with the name. Vocativ reported that Herrala, "thought it was fitting to call it Heartbleed because it was bleeding out the important information from the memory.” Because Heartbleed was such a terrible bug — security expert Bruce Schneier ranked it an 11 on a scale of 1 to 10 — it needed solid branding to get the attention it deserved. The catchy named Heartbleed, linked with the bleeding heart logo and a user-friendly website, was the perfection combination of marketing. It received the attention it needed, causing thousands of affected websites to construct patches and users to change passwords in record time.

As for some of the kookier named viruses, there's always a story behind it, usually as unique as the program itself. Melissa, one of the fastest-spreading viruses ever, was named after a stripper who programmer David Smith met in Florida. The Michelangelo virus would only activate on March 6th, the artist's birthday. Many have taken on the name of the celebrity who you are promised naked pictures of if only you click on a suspicious link. Some virus names are just glorification for their developer: Samy Kumar named the Samy Worm after himself, and the CIH virus is the initials of its developer, Chen Ing Hau. 

Regardless of how delightful the name is, be sure to run virus screenings regularly, and backup your data. I LOVE YOU affected over 50 million users and cost the U.S. $15 billion to remove. 

(Image via igor.stevanovic/

Threatwatch Alert

Accidentally leaked credentials / Misplaced data

Boeing Employee Emails 36,000 Coworkers’ Personal Info to Spouse

See threatwatch report


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.