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

10/9/2020
04:20 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Latest Version of MalLocker Android Ransomware Packs New Tricks

Like most such mobile malware, the new one doesn't encrypt data but attempts to make an infected system impossible to use, Microsoft says.

Security researchers at Microsoft have spotted a dangerous new version of MalLocker, a constantly evolving Android ransomware family that has been floating around in the wild since at least 2014.

The new version is notable for how it surfaces the ransom demand on infected devices and its integration of an open source machine-learning module for context-aware cropping of the ransom note, depending on screen size. The latest variant of MalLocker also uses a new obfuscation method to hinder code analysis and to evade detection by anti-malware tools.

Related Content:

'Unkillable' Android Malware App Continues to Infect Devices Worldwide

2020 State of Cybersecurity Operations and Incident Response

New on The Edge: Emotet 101: How the Ransomware Works -- and Why It's So Darn Effective

In a report this week, Microsoft described MalLocker as being distributed via arbitrary websites and online forums, or hidden in popular apps and video players for mobile devices. Like many other Android ransomware variants, the new MalLocker does not actually encrypt data on infected devices. Instead, it attempts to prevent users from using an infected device by displaying a ransom note over every window. Regardless of what button the user clicks, the ransom note remains on top of all other windows.

What is different in the new MalLocker variant is the manner in which it achieves this persistence. Previous Android ransomware tools took advantage of a system alert feature in the OS to display the ransomware note. But that has become almost impossible to do now because of certain platform-level changes that Google has implemented to thwart the abuse, Microsoft said.

The new variant instead abuses two other functions that are present in recent versions of Android. "First, it sets its notification as a very important notification requiring immediate user attention," says Tanmay Ganacharya, partner director, security research, at Microsoft. "This notification is wired to pop up the ransom notice," he says.

Second, the malware is designed to ensure that this notification is always displayed when the user tries to do other activities or performs other functions. "It does this by using a callback, which is a way for functions to pass a piece of code to each other," Ganacharya says.

On Android, a callback is a way for one function to let another function know that an action — such as a user pressing the Home button — is completed, he notes. The new version of MalLocker is designed to take advantage of the callback method to know when a user might have completed a specific action so it can promptly display the ransom note. "This means that whatever the user does, the ransomware's notification is always displayed, effectively preventing the user from performing any other action," Ganacharya says.

In addition, the new version of MalLocker also incorporates an open source machine-learning module that lets it know an infected device's screen size so the ransom note can be automatically resized and cropped to fit it without distortion.

According to Microsoft, the new Android malware's obfuscation tactics are also noteworthy. The manner in which the malware authors have encrypted and hidden the payload, the decryption routine it uses and the presence of lots of deliberately introduced junk code all make the malware hard to analyze and detect, Microsoft said.

Users with infected devices can try rebooting the system in safe mode and then uninstalling the malware, Microsoft said.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Cyberattacks Are Tailored to Employees ... Why Isn't Security Training?
Tim Sadler, CEO and co-founder of Tessian,  6/17/2021
Edge-DRsplash-10-edge-articles
7 Powerful Cybersecurity Skills the Energy Sector Needs Most
Pam Baker, Contributing Writer,  6/22/2021
News
Microsoft Disrupts Large-Scale BEC Campaign Across Web Services
Kelly Sheridan, Staff Editor, Dark Reading,  6/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34390
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel function where a lack of checks allows the exploitation of an integer overflow on the size parameter of the tz_map_shared_mem function.
CVE-2021-34391
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel�s tz_handle_trusted_app_smc function where a lack of integer overflow checks on the req_off and param_ofs variables leads to memory corruption of critical kernel structures.
CVE-2021-34392
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel where an integer overflow in the tz_map_shared_mem function can bypass boundary checks, which might lead to denial of service.
CVE-2021-34393
PUBLISHED: 2021-06-22
Trusty contains a vulnerability in TSEC TA which deserializes the incoming messages even though the TSEC TA does not expose any command. This vulnerability might allow an attacker to exploit the deserializer to impact code execution, causing information disclosure.
CVE-2021-34394
PUBLISHED: 2021-06-22
Trusty contains a vulnerability in all TAs whose deserializer does not reject messages with multiple occurrences of the same parameter. The deserialization of untrusted data might allow an attacker to exploit the deserializer to impact code execution.