{"id":9705,"date":"2015-09-15T09:00:46","date_gmt":"2015-09-15T13:00:46","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=9705"},"modified":"2019-11-15T07:01:59","modified_gmt":"2019-11-15T12:01:59","slug":"fact-or-fiction-virus-damaging-hardware","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/fact-or-fiction-virus-damaging-hardware\/9705\/","title":{"rendered":"Fact or Fiction: can a virus actually damage PC hardware?"},"content":{"rendered":"<p>In fact, it\u2019s the one of the most widely believed myths in the infosec world. At the same time, it\u2019s the most non-standard one. That double-sided nature is likely the reason why the myth is so enduring.<\/p>\n<p>At the dawn of the PC era, the late 20th century, users frequently spread scary stories that happened \u201cto one of good friends of theirs,\u201d from a virus. In such stories, viruses, for instance, fed some \u2018wrong\u2019 interlacing to a CRT monitor and \u2018burned out\u2019 the PC\u2019s hardware components. In other tales, malware made HDD plates \u2018resonate\u2019 fiercely, ultimately destroying hard drives. Or overclocked a floppy drive to cause an imminently deadly rotor overheat.<\/p>\n<p>Antivirus developers have constantly busted those myths. Sure some of these cases are theoretically plausible, but built-in foolproof protection mechanisms don\u2019t allow such failures to happen. So, as they say, sleep tight, little friends, they shall not pass, and all that kind of stuff.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>Fact or Fiction: can a #virus actually damage PC hardware? #infosec<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2F5P9B&amp;text=Fact+or+Fiction%3A+can+a+%23virus+actually+damage+PC+hardware%3F+%23infosec\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>Users pretend to be satisfied with these explanations, yet continued to believe in myths. Anything can happen, after all, with vendors hushing up things.<\/p>\n<p>Yet, life is a curious thing and full of surprises. For example, back in 1999 a massive Win95.CIH (a.k.a. Chernobyl) virus pandemic took over thousands of machines. That malware corrupted data stored both on a hard drive and on BIOS chips on motherboards. Some of the affected PCs would not start as their boot program was damaged. To level the adverse effects of the attack, one had to replace BIOS chips and rewrite the data.<\/p>\n<p><span class=\"embed-youtube\" style=\"text-align:center; display: block;\"><iframe class=\"youtube-player\" type=\"text\/html\" width=\"640\" height=\"390\" src=\"https:\/\/www.youtube.com\/embed\/RrnWFAx5vJg?version=3&amp;rel=1&amp;fs=1&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;start=90&amp;wmode=transparent\" frameborder=\"0\" allowfullscreen=\"true\"><\/iframe><\/span><\/p>\n<p>Was that effectively a physical damage inflicted on a PC? In reality, no. After a series of manipulations motherboards could be cured and returned to the operating state. But the problem could not be solved by standard \u2018home emergency kit\u2019 and required specialized equipment.<\/p>\n<p>Today, everything is even more confusing.<\/p>\n<p>First, any standalone piece of hardware is bundled with a rewritable microprogram, at times with even more than one. I\u2019m surprised this trend did not affect screws which hold this too smart hardware together.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Indestructible malware by <a href=\"https:\/\/twitter.com\/hashtag\/Equation?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#Equation<\/a> cyberspies exists, but don\u2019t panic yet: <a href=\"https:\/\/t.co\/a3rv49Cdnl\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/t.co\/a3rv49Cdnl<\/a>  <a href=\"https:\/\/twitter.com\/hashtag\/EquationAPT?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#EquationAPT<\/a> <a href=\"http:\/\/t.co\/Gaf0HCjHoY\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/Gaf0HCjHoY<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/567764207162167296?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">February 17, 2015<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Each of those microprograms has been evolving for years, having become quite a complex piece of software, which is by design potentially open to an attack. Once the attack is successful, the consequences are not always immediately remediable.<\/p>\n<p>Take the story about <a href=\"https:\/\/www.kaspersky.ru\/blog\/equation-hdd-malware\/6984\/\" target=\"_blank\" rel=\"noopener\">modified firmware of hard drives<\/a>. For the record, while analyzing the Equation cyberespionage campaign, Kaspersky Lab experts explored spyware modules injected into microprogram code for a number of different HDD models. These pieces of malware are used to gain complete control over the affected disk; which cannot be remedied even by formatting.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">The only way to remove nls_933w.dll <a href=\"https:\/\/twitter.com\/hashtag\/TheSAS2015?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#TheSAS2015<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/EquationAPT?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#EquationAPT<\/a> <a href=\"http:\/\/t.co\/zfVE1kKyha\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/zfVE1kKyha<\/a><\/p>\n<p>\u2014 Fabio Assolini (@assolini) <a href=\"https:\/\/twitter.com\/assolini\/status\/567410130934067201?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">February 16, 2015<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>One cannot change the firmware by means of a standard toolset \u2014 the firmware is responsible for updating itself. As you would expect, it puts a hell of a fight when someone tries to lure it from where it belongs. Of course, if you happen to be in possession of specialized equipment, you might be able to apply force and change any microprogram. In real life, an affected drive goes straight to the trash \u2013 it\u2019s the most cost-effective option.<\/p>\n<p>Can it be considered physical damage? Well, that\u2019s disputable. But the number of stories about <a href=\"https:\/\/www.kaspersky.ru\/blog\/hardware-malware\/7364\/\" target=\"_blank\" rel=\"noopener\">hardware-based vulnerabilities<\/a> continues to increase.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">5 threats that could affect hardware \u2013 <a href=\"http:\/\/t.co\/CP1DSfkgy3\" target=\"_blank\" rel=\"noopener nofollow\">http:\/\/t.co\/CP1DSfkgy3<\/a> <a href=\"http:\/\/t.co\/cnse35hAr3\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/cnse35hAr3<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/592735335156682752?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">April 27, 2015<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Second, it\u2019s quite unclear what kind of machine can be defined as \u2018computer.\u2019 For instance, any current car is, to some extent, a computer \u2014 and what\u2019 even more important \u2013 a connected computer on wheels. It is exposed to remote hacks and compromise, as we found out in a recent well-publicized demonstration of the <a href=\"https:\/\/www.kaspersky.ru\/blog\/remote-car-hack\/8430\/\" target=\"_blank\" rel=\"noopener\">remote hack of a Jeep Cherokee<\/a>.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\"><a href=\"https:\/\/twitter.com\/hashtag\/BlackHat?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#BlackHat<\/a> 2015: The full story of how that Jeep was hacked <a href=\"https:\/\/t.co\/y0d6k8UE4n\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/t.co\/y0d6k8UE4n<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/bhUSA?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#bhUSA<\/a> <a href=\"http:\/\/t.co\/SWulPz4Et7\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/SWulPz4Et7<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/629651596876644352?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">August 7, 2015<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Right, the hack was performed by hackers, not a virus \u2014 Ok, it was a piece of cake, given years of research this hack took. However, it won\u2019t come as a surprise if an attack like that will end up with a car hitting some pole on the roadside. I guess this can be called damage.<\/p>\n<p><strong>So, can a virus actually damage PC hardware? Is it fact or fiction?<\/strong><\/p>\n<p><strong>That\u2019s truth. However, the answer here heavily depends on what you actually mean by \u201cdamage\u201d, \u201cvirus\u201d, \u201cPC\u201d, etc.<\/strong><\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-cyberattacks\">\n","protected":false},"excerpt":{"rendered":"<p>A virus damaging hardware is one of the most widely believed myths in the infosec domain. And, at the same time, it\u2019s the most non-standard one. And it\u2019s not totally a myth, after all.<\/p>\n","protected":false},"author":521,"featured_media":9711,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5,2683],"tags":[982,1225,1226,388,36,1317,97,422,154,1227],"class_list":{"0":"post-9705","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"category-threats","9":"tag-equation","10":"tag-fact-or-fiction","11":"tag-hardware","12":"tag-infosec","13":"tag-malware-2","14":"tag-myths","15":"tag-security-2","16":"tag-threats","17":"tag-viruses","18":"tag-win95-cih"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/fact-or-fiction-virus-damaging-hardware\/9705\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/fact-or-fiction-virus-damaging-hardware\/5976\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/fact-or-fiction-virus-damaging-hardware\/6241\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/fact-or-fiction-virus-damaging-hardware\/6159\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/fact-or-fiction-virus-damaging-hardware\/6822\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/fact-or-fiction-virus-damaging-hardware\/6638\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/fact-or-fiction-virus-damaging-hardware\/8765\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/fact-or-fiction-virus-damaging-hardware\/4872\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/fact-or-fiction-virus-damaging-hardware\/5679\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/fact-or-fiction-virus-damaging-hardware\/6155\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/fact-or-fiction-virus-damaging-hardware\/8794\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/fact-or-fiction-virus-damaging-hardware\/8765\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/fact-or-fiction-virus-damaging-hardware\/9705\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/fact-or-fiction-virus-damaging-hardware\/9705\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/equation\/","name":"Equation"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9705","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/521"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=9705"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9705\/revisions"}],"predecessor-version":[{"id":30405,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9705\/revisions\/30405"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/9711"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=9705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=9705"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=9705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}