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

4/8/2020
04:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

'Unkillable' Android Malware App Continues to Infect Devices Worldwide

The xHelper Trojan has compromised over 55,000 devices so far, Kaspersky says.

More than 55,000 Android devices worldwide have been infected with malware that security vendor Kaspersky this week described as virtually irremovable for most users.

Kaspersky first observed the xHelper Android Trojan malware being used in mass attacks last year. Months later, the malware remains as active as ever and continues to pose a threat to Android users everywhere, according to the vendor.

Like most Android malware, xHelper is being distributed under the guise of legitimate apps — in this case, as "cleaners" and "speed-up" apps for Android smartphones. xHelper is also being downloaded by malware that comes preinstalled on Android smartphones from some device manufacturers, Kaspersky said. Users typically most at risk of their devices becoming infected are those who download apps from unofficial, third-party Android application stores.

Once installed on a device, the malware collects unique device information, such as android_id, manufacturer, model, and other data useful for targeted advertising purposes, says Igor Golovin, security expert at Kaspersky.

"xHelper significantly reduces the performance of the device and constantly displays intrusive ads," Golovin says. "Our test device turned out to be practically unusable after infection."

Mobile malware is a growing concern for enterprise organizations, especially those that permit the use of unmanaged and personally owned smartphones and tablets for work. Though attacks against mobile devices have not quite materialized in the way security experts have predicted so far, many believe it is only a matter of time before threat actors start attacking smartphone and tablet users more heavily. Numerous mobile malware tools have surfaced in recent years, including banking Trojans, spyware, tracking software, and cryptominers.

Many believe that Android devices will pose a bigger risk to enterprise security than devices running iOS because of the sheer number of malware tools targeting Android.

Particularly Persistent
What makes xHelper particularly dangerous is its ability to stay put on an infected device even if the user deletes the malware and restores the device to factory settings. Once the app is installed, it disappears and cannot be found either in the program menu or on the main screen of the device, Kaspersky said. The only place it appears is in the list of installed apps in the system settings.

The malware downloads multiple other malicious files, including one called "Triada" that enables root access to the infected device. The root access allows xHelper to install malware directly into the system partition that is mounted at device start-up, Kaspersky said.

Typically, the partition is mounted in read-only mode, but the Trojan uses its root privileges to mount it in write mode so malware programs can be installed there. All files copied to the phone are designated as "immutable," meaning they cannot be deleted even by a user with the requisite level of administrative privileges.

"This malware utilizes root access and installs additional malicious code deep into the system and its recovery mechanism," Golovin says.

Since the code is installed using root access, it cannot be removed without it. However, this access level is not normally available to users or applications on Android, Golovin notes. "Basically, this malware is protected after installation by the system itself and its security mechanisms," he says.

Detecting the malware is difficult as well because the Trojan downloads and decrypts its payloads one after another multiple times in a manner reminiscent of Russian Matryoshka nesting dolls, he says. Most of the devices on which xHelper has gained root access so far have been running Android versions 6 and 7 from Chinese manufacturers.

Kaspersky researchers have found xHelper impacting Android devices around the world. But users in some regions have been impacted more than other regions. The differences are likely due to the heavier use of devices with preinstalled malware from some manufacturers in certain countries, Golovin says.

Related Content:

A listing of free security products and services compiled for Dark Reading by Omdia analysts to help you meet the challenges of COVID-19. 

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
rhiltbrunn
50%
50%
rhiltbrunn,
User Rank: Apprentice
4/8/2020 | 9:41:03 PM
Possible fix for some who are infected with xHelp...
This is a very good article about a nasty bug on the Android platform.

There is a possible solution for some, if they are a bit technically minded, on the Malwarebytes blog site.

Here's the link:

https://blog.malwarebytes.com/android/2020/02/new-variant-of-android-trojan-xhelper-reinfects-with-help-from-google-play/

It may not be a solution to everyone's problem, but it might be a start for the more intrepid.

Cheers!
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.