recommended reading

How Computer Viruses Get Their Names

igor.stevanovic/Shutterstock.com

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/Shutterstock.com)

Threatwatch Alert

Credential-stealing malware / User accounts compromised / Software vulnerability

Android Malware Infects More than 1M Phones, Adds 13,000 Devices a Day

See threatwatch report

JOIN THE DISCUSSION

Close [ x ] More from Nextgov
 
 

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

  • 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.

    Download
  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

    Download
  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

    Download
  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download

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