{"id":436,"date":"2010-08-11T00:00:00","date_gmt":"2010-08-11T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/08\/11\/first-sms-trojan-for-android-is-in-the-wild\/"},"modified":"2021-12-30T11:37:19","modified_gmt":"2021-12-30T11:37:19","slug":"first-sms-trojan-for-android-is-in-the-wild","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/08\/11\/first-sms-trojan-for-android-is-in-the-wild\/","title":{"rendered":"First SMS Trojan for Android is in the wild"},"content":{"rendered":"<p>The first text message-based Trojan to infect smartphones running Google&#8217;s Android operating system has been detected in the wild.  Trojan-SMS.AndroidOS.FakePlayer-A poses as a harmless media player application and has already infected a number of mobile devices, Russian security firm Kaspersky Lab warns.  In a statement, Google said it existing permission controls guard against this type of type, which only exist for applications published outside the Android Marketplace.  Users must explicitly approve this access in order to continue with the installation, and they may uninstall applications at any time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There have been isolated cases of devices running Android getting infected with spyware since last year, but this is the first occasion that an SMS-spewing Trojan, common in the world of mobile malware, has affected devices running Google&#8217;s operating system.<\/p>\n<p>If a user agrees to permit an application to access premium rate service during installation, the smartphone may then be able to make calls and send SMSs without further authorisation.<\/p>\n<p>http:\/\/www.theregister.co.uk\/2010\/08\/10\/android_sms_trojan\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[],"class_list":["post-436","post","type-post","status-publish","format-standard","hentry","category-mobility"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=436"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/436\/revisions"}],"predecessor-version":[{"id":2923,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/436\/revisions\/2923"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}