{"id":3541,"date":"2014-06-20T12:30:47","date_gmt":"2014-06-20T16:30:47","guid":{"rendered":"http:\/\/me-en.kaspersky.com\/blog\/?p=3541"},"modified":"2020-02-26T18:58:45","modified_gmt":"2020-02-26T14:58:45","slug":"week_news_mobile_malware_birthday","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/week_news_mobile_malware_birthday\/3541\/","title":{"rendered":"A Week in the News: Mobile Malware&#8217;s Tenth Birthday"},"content":{"rendered":"<p>In the news this week: it\u2019s been 10 years since the first known worm targeting mobile devices emerged. We\u2019ll also check in on the latest Android security and privacy news as well as a couple of data breaches that spilled sensitive user information. As always we\u2019ll let you know about any patches that are available. This and more below:<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05111352\/malware-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5160\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/06\/05111352\/malware-1.png\" alt=\"malware\" width=\"640\" height=\"480\"><\/a><\/p>\n<p><strong>The First Mobile Worm<\/strong><\/p>\n<p>A decade ago this week, the first ever mobile malware emerged on Nokia\u2019s now-nearly-extinct Symbian platform. \u2018Cabir\u2019 \u2013 as it came to be known \u2013 was not discovered in the wild by a complicated network of detection systems like much of today\u2019s malware samples. It was quite literally handed to what was then the much younger, 2004-version of Kaspersky Lab.<\/p>\n<p>It was a simpler time in terms of malware and Cabir was something of a simple worm, relatively speaking. The worm spread via Bluetooth, which was likely novel at the time, but is fairly commonplace now. Perhaps <a href=\"https:\/\/threatpost.com\/ten-years-later-cabir-worms-place-in-history-is-unique\/106679\" target=\"_blank\" rel=\"noopener nofollow\">the strangest aspect to Cabir is that it didn\u2019t actually do anything<\/a> beyond propagating to nearby, Bluetooth enabled phones and displaying the word \u201cCaribe\u201d on the screens then and every time a user turned his or her phone on.<\/p>\n<p>Kaspersky Lab tested the worm out on a Nokia N-Gage, which you may or may not remember. Luckily, if your curious, we put together <a href=\"https:\/\/www.kaspersky.com\/blog\/cabir-10\/\" target=\"_blank\" rel=\"noopener nofollow\">a slideshow showing the sorts of phones Cabir would have infected<\/a>.<\/p>\n<p><strong>Android News<\/strong><\/p>\n<p>Just yesterday, Government officials in the United States announced that <a href=\"https:\/\/threatpost.com\/google-microsoft-to-implement-mobile-kill-switch\/106778\" target=\"_blank\" rel=\"noopener nofollow\">Google and Microsoft would implement \u2018kill switch\u2019 features <\/a>into their Android and Windows Mobile operating systems. It may strike you as odd that government officials \u2013 rather than officials from Google or Microsoft \u2013 would make such an announcement. However, in recent years there\u2019s been an alarming increase in smartphone theft. Unfortunately, these crimes are often violent, resulting in injury and even loss of life.<\/p>\n<div class=\"pullquote\">As it turns out, studies have shown that in the period of time that Apple\u2019s \u201c<a href=\"https:\/\/www.kaspersky.com\/blog\/ios-7-new-security-features\/\" target=\"_blank\" rel=\"noopener nofollow\">Activation Lock<\/a>\u201d feature has been available, iPhone theft has steadily decreased.<\/div>\n<p>A international conglomeration of elected and law enforcement officials recognized that violent, smartphone related crime was a problem, so they launched the Secure Our Smartphones (S.O.S.) initiative. S.O.S. was intended to convince Microsoft and Google to implement a feature that would render a mobile device useless if stolen. Of course, Apple had already done so with its \u201cActivation Lock\u201d feature, which makes it impossible for a thief to unlock a stolen phone without the proper user\u2019s iCloud username and password.<\/p>\n<p>As it turns out, studies have shown that in the period of time that Apple\u2019s \u201cActivation Lock\u201d feature has been available, iPhone theft has steadily decreased. Tellingly, over the same period of time, thefts targeting devices without a \u2018kill switch\u2019 feature continue to increase. Yesterday\u2019s announcement means that in the coming months, the most recent version of the mobile operating systems on some 97 percent of U.S. smartphones will have a \u2018kill switch\u2019 feature.<\/p>\n<p><strong>Data Breaches\u2026 Again<\/strong><\/p>\n<p>Just two data breaches this week: one <a href=\"https:\/\/threatpost.com\/hackers-breach-dominos-france-demand-ransom-payment\/106673\" target=\"_blank\" rel=\"noopener nofollow\">affecting some 600,000 Domino\u2019s customers<\/a> \u2013 mostly in France but also in Belgium as well \u2013 and another at AT&amp;T affecting an unknown number of the mobile carrier\u2019s customers. The <a href=\"https:\/\/threatpost.com\/att-warns-customers-of-data-breach\/106681\" target=\"_blank\" rel=\"noopener nofollow\">breach at AT&amp;T<\/a> spilled mobile users\u2019 birth dates and Social Security numbers. The breach at Domono\u2019s spilled customers\u2019 full names, addresses, phone numbers, email addresses, passwords, delivery instructions, and favorite pizza toppings.<\/p>\n<p>Interestingly in the case of Domino\u2019s, a hacker group claiming responsibility for the attack demanded a \u20ac30,000 ransom payment in exchange for the information gleaned in the attack. Domino\u2019s officials said there was no financial information included in the breach. They have since fixed the bugs that led to the breach and have no intention of paying any ransom.<\/p>\n<p><strong>Patches<\/strong><\/p>\n<p>Last but not least, the popular router brand<a href=\"https:\/\/threatpost.com\/blekin-patches-directory-traversal-bug-in-wireless-router\/106723\" target=\"_blank\" rel=\"noopener nofollow\"> Belkin has patched a serious vulnerability<\/a> in its N150 wireless router. The bug could give an attacker access to any system files on affected routers, which could enable a number of malicious actions. If you are using that brand and make of router, it is recommended that you install the firmware update as soon as possible, which isn\u2019t easy to do. You\u2019ll have to go to the Belkin N150 website and download the latest version of the firmware. Then you\u2019ll have to log into your router and upload the new firmware. We do have an article with some generic instructions on <a href=\"https:\/\/www.kaspersky.com\/blog\/securely-configuring-a-wireless-router\/\" target=\"_blank\" rel=\"noopener nofollow\">how to install firmware on a router<\/a>.<\/p>\n<p><strong>In Other News<\/strong><\/p>\n<p>The United States Federal Trade Commission is calling on hackers attending the DEF CON hacker conference to develop technologies that can successfully lure in and identify the perpetrators of illegal robocalling scams. <a href=\"https:\/\/threatpost.com\/ftc-asking-def-con-to-help-catch-robocallers\" target=\"_blank\" rel=\"noopener nofollow\">Read more at Threatpost<\/a>.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>A review of this week\u2019s #security and #privacy headlines with @TheBrianDonohue:<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2Fg6xZ&amp;text=A+review+of+this+week%26%238217%3Bs+%23security+and+%23privacy+headlines+with+%40TheBrianDonohue%3A\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>This week: the first mobile malware turns 10; we check in on Android security news and recent data breaches; and we fill you in on the week&#8217;s patches.<\/p>\n","protected":false},"author":42,"featured_media":3542,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[105,314,512,681,43,268],"class_list":{"0":"post-3541","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-android","9":"tag-data-breach","10":"tag-mobile-malware","11":"tag-patch","12":"tag-privacy","13":"tag-vulnerabilities"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/week_news_mobile_malware_birthday\/3541\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/week_news_mobile_malware_birthday\/3643\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/week_news_mobile_malware_birthday\/3984\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/week_news_mobile_malware_birthday\/4228\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/week_news_mobile_malware_birthday\/4389\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/week_news_mobile_malware_birthday\/5159\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/week_news_mobile_malware_birthday\/4003\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/week_news_mobile_malware_birthday\/4389\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/week_news_mobile_malware_birthday\/5159\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/week_news_mobile_malware_birthday\/5159\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/android\/","name":"Android"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=3541"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3541\/revisions"}],"predecessor-version":[{"id":15821,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3541\/revisions\/15821"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/3542"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=3541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=3541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=3541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}