{"id":19480,"date":"2020-03-05T08:14:41","date_gmt":"2020-03-05T13:14:41","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/apt-collateral-damage\/19480\/"},"modified":"2020-04-14T21:37:13","modified_gmt":"2020-04-14T16:07:13","slug":"apt-collateral-damage","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/apt-collateral-damage\/19480\/","title":{"rendered":"Collateral damage from APTs"},"content":{"rendered":"<p>Folks usually relate to APTs about the same way we relate to espionage in general: It\u2019s certainly a big deal, but it won\u2019t hit us mere mortals, right? Most of us don\u2019t carry any significant industrial or government secrets on our phones and don\u2019t work with classified information on our computers, so why would we be of interest to them?<\/p>\n<p>Well, folks are mostly right. It\u2019s very unusual for the average person to be targeted by a nation-state\u2013sponsored actor, but we can still be collateral damage. Daniel Creus of Kaspersky\u2019s Global Research and Analysis Team (GReAT) spoke on that topic recently in Barcelona. This post quickly recaps it and describes the three ways ordinary people can run afoul of an APT attack.<\/p>\n<h2>Collateral damage scenario #1: The wrong website at the wrong time<\/h2>\n<p>In comparison with smaller actors, APTs have enough money for a bunch of zero-day exploits, including the ones that make remote <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/watering-hole\/\" target=\"_blank\" rel=\"noopener noreferrer\">watering hole<\/a> attacks possible. <a href=\"https:\/\/googleprojectzero.blogspot.com\/2019\/08\/a-very-deep-dive-into-ios-exploit.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Research by Google Project Zero in 2019<\/a> revealed that one actor used as many as 14 different vulnerabilities in 5 different exploit chains to infect their targets with spyware.<\/p>\n<p>Some of these vulnerabilities were used to remotely infect iOS users who visited specific politics-related websites. They ended up with spyware on their phones. The thing is, the actor did not distinguish among website visitors, meaning that <em>all<\/em> iOS users who visited the site got infected, regardless of whether they were of any interest to the actor.<\/p>\n<p>And that was hardly the only APT attack that involved a watering hole. For example, one of the attack vectors of the infamous <a href=\"https:\/\/www.kaspersky.com\/blog\/new-ransomware-epidemics\/17314\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">NotPetya (aka ExPetr)<\/a> started with the infection of a government website. When users visited the website, malware was downloaded and executed on their computers. You may remember that NotPetya had tremendous collateral damage.<\/p>\n<p>So, one of the problems with APTs is that threat actors may have no interest in targeting you in particular, but if you happen to visit the wrong website or download the wrong app, you will get infected nevertheless, and the private information from your device will be exposed to them \u2014 or damaged, in APT-related ransomware cases such as NotPetya.<\/p>\n<h2>Collateral damage scenario #2: Serious toys in cybercriminals\u2019 hands<\/h2>\n<p>Among other things, APTs often seek the secrets of other APTs. They tend to hack each other and sometimes leak the tools that their foes use. Other, smaller and less advanced actors pick them up and use them to create malware, which sometimes gets out of control. Remember, the infamous <a href=\"https:\/\/www.kaspersky.com\/blog\/wannacry-ransomware\/16518\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">WannaCry wiper<\/a> was created using EternalBlue, one of the exploits leaked by ShadowBrokers when they decided to publish the Equation Group\u2019s arsenal of cyberweapons.<\/p>\n<p>More threats, including NotPetya\/ExPetr, <a href=\"https:\/\/www.kaspersky.com\/blog\/bad-rabbit-ransomware\/19887\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Bad Rabbit<\/a>, EternalRocks, and others, relied on the EternalBlue exploit as well. One leaked exploit resulted in a series of several huge epidemics and many smaller events that together affected hundreds of thousands of computers and disrupted the work of numerous businesses and government agencies around the world.<\/p>\n<p>In summary, the second problem ordinary people face with APTs is that threat actors create really dangerous tools and sometimes fail to contain them. As a result, these dangerous things can end up in the hands of cybercriminals \u2014 of varying degrees of competence \u2014 who don\u2019t hesitate to use them, sometimes affecting lots of innocent people.<\/p>\n<h2>Collateral damage scenario #3: Leak of collected data<\/h2>\n<p>As we mentioned above, the actors behind APTs have a tendency to hack each other. Sometimes they publish not only the tools they loot, but also any information their foes harvested using those tools. For example, that\u2019s how the data harvested by the infamous cyberespionage tool <a href=\"https:\/\/securelist.com\/whos-who-in-the-zoo\/85394\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">ZooPark<\/a> became publicly available.<\/p>\n<p>In the past two years, as many as 13 stalkerware vendors either were hacked or left the information they collected exposed online, on an unprotected, publicly available Web server. Leaks afflict more serious actors as well; the creators of the notorious FinFisher <a href=\"https:\/\/www.zdnet.com\/article\/top-govt-spyware-company-hacked-gammas-finfisher-leaked\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">were hacked<\/a>, and the even more notorious <a href=\"https:\/\/arstechnica.com\/information-technology\/2016\/04\/how-hacking-team-got-hacked-phineas-phisher\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Hacking Team<\/a>, which used to develop surveillance tools, has also been hacked.<\/p>\n<p>So, there\u2019s the third problem: Even if an APT has nothing to do with average users, even if it just stockpiles their information without using it against them, if that APT leaks data, smaller fish will gladly feed on that information to extort or to search for private data \u2014 from credit card numbers and document scans all the way to contact info and compromising photos.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-cyberattacks\">\n<h2>How to stay safe from APTs<\/h2>\n<p>Although APTs are significantly more sophisticated than the average malware, the same techniques we use against common threats help protect against APTs.<\/p>\n<ul>\n<li>Disable installation of apps from third-party sources on Android phones. If you really need to install some trusted app from outside Google Play, allow it once, but don\u2019t forget to change the setting back when you\u2019re done.<\/li>\n<li>Regularly check <a href=\"https:\/\/www.kaspersky.com\/blog\/android-8-permissions-guide\/23981\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">permissions of the apps<\/a> you have installed on your device and revoke any permissions you think are not necessary for a certain app. It\u2019s also a good idea to check the list of permissions an app uses before installing it. You can find the list in Google Play.<\/li>\n<li>Avoid visiting shady websites and clicking links from sources you do not completely trust. Unknown people won\u2019t send you links and apps with good intentions. Some APTs are capable of infecting legitimate websites, but many rely on good old phishing.<\/li>\n<li>Use a <a href=\"https:\/\/www.kaspersky.co.in\/advert\/security-cloud?icid=in_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____ksc___\" target=\"_blank\" rel=\"noopener\">reliable security solution<\/a> that scans everything that is about to be installed or downloaded on the device and checks every link and every package. Consider it a last line of defense: Even if a bad actor tricks you or uses an exploit to find their way into your device, the security solution can still protect you.<\/li>\n<\/ul>\n<p><!-- Put this code to the place, where the Widget will be --><\/p>\n<div id=\"privacy-widget\"><\/div>\n<p><script src=\"https:\/\/privacy.kaspersky.com\/js\/widget.js\"><\/script><br>\n<script>\n    Privacy.init({'lang':\"en\", \"responsive\": true})\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>How APTs compromise the privacy and security of average citizens that they do not target directly.<\/p>\n","protected":false},"author":675,"featured_media":19481,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2196],"tags":[483,36,2064,43,527,2045,2897],"class_list":{"0":"post-19480","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-apt","9":"tag-malware-2","10":"tag-notpetya","11":"tag-privacy","12":"tag-threats","13":"tag-wannacry","14":"tag-zoopark"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/apt-collateral-damage\/19480\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/apt-collateral-damage\/16085\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/apt-collateral-damage\/8046\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/apt-collateral-damage\/21115\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/apt-collateral-damage\/19374\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/apt-collateral-damage\/17859\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/apt-collateral-damage\/22031\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/apt-collateral-damage\/20802\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/apt-collateral-damage\/27588\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/apt-collateral-damage\/7882\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/apt-collateral-damage\/33929\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/apt-collateral-damage\/14438\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/apt-collateral-damage\/14506\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/apt-collateral-damage\/13137\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/apt-collateral-damage\/23236\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/apt-collateral-damage\/11208\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/apt-collateral-damage\/25085\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/apt-collateral-damage\/21811\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/apt-collateral-damage\/26998\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/apt-collateral-damage\/26837\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/threats\/","name":"threats"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/19480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/675"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=19480"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/19480\/revisions"}],"predecessor-version":[{"id":20236,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/19480\/revisions\/20236"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/19481"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=19480"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=19480"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=19480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}