Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Mobile

SLocker Ransomware Variants Surge

SLocker, one of the top 20 Android malware families, has seen a six-fold increase in the number of new versions over the past six months.

New variants of an Android ransomware family have surged over the past six months to some 600 unique versions.

That's a dramatic jump from the 100 variants created between October to the start of December, says Michael Covington, vice president of product strategy for Wandera, which published new data on the ransomware today.

The new strains of the mobile ransomware use a range of disguises to avoid detection. The SLocker variations are repackaged as altered icon, for example, or offer unique resources and executable files. SLocker encrypts images, documents, and videos, as well as blocks access to the device before demanding payment to unlock the phone and its contents.

Chief security officers and their teams have reason to worry about the rapid rise in the number of SLocker strains, say security experts. The malware has morphed beyond just locking users' screens on their Android devices and demanding payment, to taking over administrative rights and controlling the device, including its microphone, speakers, and the camera.

Bogdan Botezatu, senior e-threat analyst with Bitdefender, says an Android smartphone infected with SLocker could potentially broadcast highly sensitive information presented during a closed-door boardroom meeting without the user's knowledge, for example.

Wandera's Covington points to potential risks to sales and consulting staff, for example. "In a lot of situations where the employees work out in the field like in sales or consulting, it can have a massive impact on their business if they are locked out of their phone and data," he explains.

Victim organizations paid an estimated $10 million in ransom to unlock confidential data stored on Android phones that fell victim to SLocker, according to Wandera's report.

By the Numbers

Android ransomware first emerged in 2014, after creators of the Reveton/IcePol ransomware for PCs turned their attention to Android devices and cooked up the Android.Trojan. Koler.A and then later Android.Trojan.SLocker, according to Bitdefender's Botezatu.

For the first two years, SLocker was among the top 20 Android malware families and then shot up to the top 10 in 2016, notes Botezatu. "Its rise to the top 10 was mostly because of the frustration factor. It's a psychological thing when people can't get information from their smartphone," he says. "People were willing to pay the ransom. The mobile device is more personal than the personal computer."

But now SLocker ranks in the No. 14 to No. 18 spot among the top 20 Android malware families, as cyberthieves create new types of Android malware and enlarge the pool of contenders and dilute SLocker's influence, Botezatu says.

Related Content:

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Google Cloud Debuts Threat-Detection Service
Robert Lemos, Contributing Writer,  9/23/2020
Shopify's Employee Data Theft Underscores Risk of Rogue Insiders
Kelly Sheridan, Staff Editor, Dark Reading,  9/23/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...