Risk

3/7/2013
09:32 AM
50%
50%

Malware Writers Prefer Android

A whopping 96% of all smartphone malware was written for Android in Q4 2012, reports F-Secure.

Owners of Android smartphones have more to worry about than their peers, according to a new security report published Thursday from F-Secure. During the fourth quarter of 2012, 96% of all malware was written for Android, which has become the biggest target for ne'er-do-wells.

F-Secure compiled data from 2010, 2011 and 2012 to provide a picture of the state of smartphone security. It proves at least one major point: it's costly to be popular. "The rise of Android malware can be largely attributed to the operating system's increasing foothold in the mobile market," wrote F-Secure (PDF).

In 2010, Nokia's Symbian platform was the most targeted by malware writers. F-Secure said 62.5% of all malware written in 2010 was directed at Symbian, which was the dominant smartphone platform at the time. Following Symbian, 23.75% of malware targeted Microsoft's Windows Mobile platform. Just 11.25% of malware targeted Android in 2010, which was then just catching up to Apple's iOS and BlackBerry's OS in popularity. F-Secure noted that there were 80 malware families and variants in 2010.

The number of malware families surged to 195 in 2011, and so shifted the platforms targeted by malware writers. Actutally, the tables turned entirely. Fully two-thirds of all malware written in 2011 was aimed at Android, with Symbian trailing at 29.7%. Windows Mobile fell off the malware map, with just 1% of malware targeted at Microsoft's still-fading legacy smartphone platform. Android was quickly ascending to the top of the smartphone world by 2011.

[ Want the latest on mobile market share? Read Apple iPhone Gains U.S. Market Share. ]

The picture changed less dramatically in 2012. By the close of the year, 79% of all malware was written for Android (with the fourth-quarter's number leaping to an astonishing 96%). Malware written for Symbian dropped further to 19% for the full year. Only 0.7% of malware written in 2012 targeted Windows Mobile. Malware written for BlackBerry and iOS appeared for the first time, said F-Secure, with 0.3% targeting BlackBerry and 0.7% targeting iOS. The number of malware families climbed to a total of about 301.

What's the big deal with malware? F-Secure said, "Malicious actions carried out by these programs include (but are not limited to) installing hidden objects as well as hiding the objects from the user, creating new malicious objects, damaging or altering any data without authorization, and stealing any data or access credentials." These are all distinct possibilities for any device infected by malware.

Trojans are the biggest threat, representing two-thirds of the malware in 2012. Other threats include spyware, riskware, hack tools, monitoring tools and adware. Malware arrives most commonly via SMS or premium SMS messages/notifications.

It is worth pointing out that the author of this report, F-Secure, sells mobile security products and certainly has an agenda. It wants consumers and businesses to adopt its mobile security and protection products. It is also worth mentioning that in 10 years as a smartphone owner, I've never once experienced, witnessed or even heard of a malware problem affecting anyone. Is there a threat? Sure, but it isn't all that significant, in my opinion.

Here's a pro tip to avoid malware: Don't click on random SMS messages that show up from unknown sources, and only download apps from the Google Play Store (or your official mobile app store).

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Ninja
3/7/2013 | 10:28:56 PM
re: Malware Writers Prefer Android
This isn't really a surprise. Android has big enough numbers to make it a platform worth targeting, and Apple's walled garden approach to apps makes it harder (though not impossible) to slip malicious software into its app store.

Drew Conry-Murray
Editor, Network Computing
Microsoft Word Vuln Went Unnoticed for 17 Years: Report
Kelly Sheridan, Associate Editor, Dark Reading,  11/14/2017
Companies Blindly Believe They've Locked Down Users' Mobile Use
Dawn Kawamoto, Associate Editor, Dark Reading,  11/14/2017
New Locky Ransomware Takes Another Turn
Kelly Sheridan, Associate Editor, Dark Reading,  11/10/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Managing Cyber-Risk
An online breach could have a huge impact on your organization. Here are some strategies for measuring and managing that risk.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.