{"id":35330,"date":"2020-05-12T07:00:15","date_gmt":"2020-05-12T11:00:15","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=35330"},"modified":"2020-12-25T11:47:46","modified_gmt":"2020-12-25T16:47:46","slug":"ransomware-collateral-damage","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/ransomware-collateral-damage\/35330\/","title":{"rendered":"Ransomware: Collateral damage"},"content":{"rendered":"<p>You might think a ransomware-infected ATM, a timetable showing an extortionist\u2019s message at the airport, or a slot machine demanding a ransom in bitcoins would be the stuff of urban legend. Nevertheless, people observed all those things during the WannaCry ransomware epidemic three years ago. Therefore, today, Anti-Ransomware Day, seems like an opportune time to reminisce about those peculiar cases.<\/p>\n<p>Who would even think of infecting a payment terminal with ransomware? What could the payoff possibly be? The truth is that the creators of WannaCry did not choose explicit targets for their malware. It entered the network through ordinary personal computers and infected every device that it could reach through an unpatched vulnerability in the SMB protocol. That means the ransomware infected quite a few devices that did not\u00a0\u2014 could\u00a0not \u2014 contain data valuable enough to ransom. The devices were collateral damage.<\/p>\n<p>Many other types of malware are similar but missing WannaCry\u2019s convenient spreading mechanism, but the creators of those other cryptors do share a lack of consideration in targets. So, sometimes devices that pose no financial gain for attackers still fall victim to ransomware. Today\u2019s roundup of the most unusual devices that have been infected by ransomware shows you how random the victims of such attacks can be.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2020\/05\/12070058\/Anti-Ransomware_Day_logotype_color_Screen.png\"><img decoding=\"async\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2020\/05\/12070058\/Anti-Ransomware_Day_logotype_color_Screen.png\" alt=\"\" width=\"1000\" height=\"384\" class=\"aligncenter size-full wp-image-35336\"><\/a><\/p>\n<h2>1. Medical equipment<\/h2>\n<p>The photo <a href=\"https:\/\/www.forbes.com\/sites\/thomasbrewster\/2017\/05\/17\/wannacry-ransomware-hit-real-medical-devices\/#62b12c95425c\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">published on Forbes<\/a> shows the screen of a medical device that is used to improve the quality of the image obtained from an MRI machine and tracks the flow of the contrast agent to the patient. There is no need to explain how important it is to provide a timely diagnosis for a patient using magnetic resonance imaging. And what if such a device were sabotaged right in the middle of a procedure?<\/p>\n<h2>2. Traffic cameras<\/h2>\n<p>Cyberattacks have hit the cameras that record traffic violations since long before the Wanna\u0421ry epidemic. But usually it was about illegal access or sabotage. However, 590 drivers in the Australian state of <a href=\"https:\/\/www.itnews.com.au\/news\/vic-police-cancels-590-road-fines-after-wannacry-infection-466202\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Victoria can thank malware for saving them from having to pay fines<\/a>. According to <em>ITNews<\/em>, the infected cameras remained fully operational. The police simply did not collect fines using that particular evidence because the moving violations were recorded by compromised devices.<\/p>\n<h2>3. ATMs<\/h2>\n<p>WannaCry hit ATMs <a href=\"https:\/\/www.indiatoday.in\/india\/story\/atms-shut-down-india-wanna-cry-ransomware-attack-977191-2017-05-15\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">all around the world<\/a>. Reinstalling the operating system restored infected ATMs, but doing so takes time, especially in cases of mass infection. What is more, these devices are usually connected to the same network and have the same protection, so if it fails for one, it fails for all. Although the cash stored inside the ATMs was in no danger, many banks had to work hard to rebuild their ATM networks \u2014 not to mention their damaged reputations.<\/p>\n<h2>4. Arrival and departure screens<\/h2>\n<p>WannaCry even hit some <a href=\"https:\/\/www.ft.com\/content\/404ad0b2-388f-11e7-821a-6027b8a20f23\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">arrival and departure screens in airports and railway stations<\/a>. It is unlikely that anyone would pay a ransom here \u2014 absolutely no valuable information is stored in those devices. Nevertheless, it costs both time and money to restore such a board. Nonfunctioning screens at train stations and airports can also cause passengers a lot of trouble. And if passengers are unable to get to their destination on time because of malware, whom will they hold liable?<\/p>\n<h2>5. Outdoor advertising signs<\/h2>\n<p>Billboards also fell victim to ransomware. Looking past the sarcastic remarks from passersby and the annoyance of those sent out to repair or replace the displays, the main victims were advertisers, which suffered significant losses of reputation. After all, they are paid to display their clients\u2019 videos or ads, and screens stuck showing ransomware messages violate customer contracts. Such problems can also discourage companies from continuing to use the services of the affected advertising firm.<\/p>\n<h2>6. Parking payment terminals<\/h2>\n<p>Consider returning to a parking garage only to see a <a href=\"https:\/\/nltimes.nl\/2017\/05\/15\/dutch-police-call-citizens-report-cyberattacks-following-global-ransomware-attack\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">ransom demand on the payment terminal<\/a>. Now you can\u2019t pay for your parking, which means that the gate arm will not rise when you try to exit the garage. But the main victim here, of course, is the parking garage operator. Everyone who is now unable to park in the garage or leave the facility in a timely manner will be angry at the company.<\/p>\n<h2>7. Ticket machines<\/h2>\n<p>Ticket vending machines were also infected. For example, <a href=\"https:\/\/www.kaspersky.com\/blog\/mamba-hddcryptor-ransomware\/13539\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">in San Francisco, ticket machines for the BART subway system remained out of order for two days as a result of a Mamba ransomware<\/a> <u>attack<\/u>. The attackers demanded $73,000 from the rapid transit operator. However, the injured party (rightly) refused to pay the ransom, and as a result, the San Francisco Municipal Transportation Agency was forced to give out free subway tickets until the machines could be repaired.<\/p>\n<h2>Practical takeaways<\/h2>\n<p>The devices unintentionally infected with ransomware were hit largely because their operators saw no need to install up-to-date protective solutions and to update their operating systems in a timely manner. As we\u2019ve seen in practice, many people don\u2019t know that these types of equipment are just computers, that they tend to run some variety of Windows, and that they exhibit the vulnerabilities of their OS family.<\/p>\n<p>Therefore, if your company uses this kind of equipment, then we have the following recommendations for you:<\/p>\n<ul>\n<li>Move those machines to a separate subnet to isolate them from other computers;<\/li>\n<li>Install operating system patches in a timely fashion;<\/li>\n<li>Install appropriate protective solutions.<\/li>\n<\/ul>\n<p>In fact, our lineup includes specialized protection for these types of devices: <a href=\"https:\/\/www.kaspersky.com\/enterprise-security\/embedded-systems?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky Embedded Systems Security<\/a> protects even low-power embedded computers of the kind frequently found in ATMs, payment terminals, and other similar devices.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In addition to its primary targets, ransomware has infected some unusual devices.<\/p>\n","protected":false},"author":2593,"featured_media":35331,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3051,3052],"tags":[1680,420,2510],"class_list":{"0":"post-35330","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-cryptors","11":"tag-ransomware","12":"tag-wannacry"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/ransomware-collateral-damage\/35330\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/ransomware-collateral-damage\/21255\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/ransomware-collateral-damage\/16720\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/ransomware-collateral-damage\/8281\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/ransomware-collateral-damage\/22250\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/ransomware-collateral-damage\/20439\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/ransomware-collateral-damage\/18706\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/ransomware-collateral-damage\/22669\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/ransomware-collateral-damage\/21597\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/ransomware-collateral-damage\/28382\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/ransomware-collateral-damage\/8221\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/ransomware-collateral-damage\/14893\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/ransomware-collateral-damage\/15178\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/ransomware-collateral-damage\/13448\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/ransomware-collateral-damage\/23969\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/ransomware-collateral-damage\/11455\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/ransomware-collateral-damage\/28285\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/ransomware-collateral-damage\/25415\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/ransomware-collateral-damage\/22281\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/ransomware-collateral-damage\/27557\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/ransomware-collateral-damage\/27393\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/ransomware\/","name":"Ransomware"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/35330","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\/2593"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=35330"}],"version-history":[{"count":11,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/35330\/revisions"}],"predecessor-version":[{"id":38256,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/35330\/revisions\/38256"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/35331"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=35330"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=35330"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=35330"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}