Tuesday, December 3, 2024
HomeAndroidAndroid XHelper Malware Reinstall Itself Again & Again After Removed it Using...

Android XHelper Malware Reinstall Itself Again & Again After Removed it Using Advanced Persistence Technique

Published on

SIEM as a Service

Researchers uncovered a stealthy Android malware called XHelper that has unseen reinstalling capability after the malware removed from the infected Android device.

Once removed the XHelper malware from the devices, within an hour, the variants of xHelper Trojan agent was re-infecting over and over again.

We have reported the same Android Trojan xHelper in last year October when it was reportedly infected 45k Android users with similar capabilities.

- Advertisement - SIEM as a Service

Initially, researchers suspect that the reinfection occurs due to the pre-installed malware, so they run  Android Debug Bridge (adb) commands to on the infected mobile device. 

But it doesn’t work and still the malware resided in the device even they have tested the other facts including the mobile device’s system updater, and an audio app with hits on VirusTotal, a potential indicator of maliciousness and applied various rules.

Discovering xHelper Reinstalling Medium

After a long duration of testing the Android device that infected by the xHelper over and over by admitting the various infection facts, finally, they spotted the infection medium was Google Play.

So once the Google play disabled, then the malware infection was stopped, and also they suspected that the Google Play wasn’t infected with the malware and something within Google Play was triggering the re-infection—perhaps something that was sitting in storage.

Hackers using Google Play as a Smokescreen, but in reality, the Xhelper was installed from some other place, and they have started searching for anything that started with com.mufc.

Finally spotted the place in local File explorer with a directory named com.mufc.umbtts was yet another Android application package (APK). 

According to Malwarebytes report, The APK in question was a Trojan dropper we promptly named Android/Trojan.Dropper.xHelper.VRW. It is responsible for dropping one variant of xHelper, which subsequently drops more malware within seconds.

Since there is no sign of appearing that Trojan.Dropper.xHelper.VRW is installed, researchers believe that the malware has the persistent capability of evading the detection it installed, ran, and uninstalled again within seconds.

It strongly teaches that the directories and files remain on the Android mobile device even after a factory reset.

so there are high chances of the device will keep getting infected until the directories and files are removed.

Some users said that they suppressed Xhelper activity by turning off permissions and locking them using app lock software. Some users said that “tried denying permissions to xHelper without uninstalling, but it turned on all permissions again.”

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

PEFT-As-An-Attack, Jailbreaking Language Models For Malicious Prompts

Federated Parameter-Efficient Fine-Tuning (FedPEFT) is a technique that combines parameter-efficient fine-tuning (PEFT) with federated...

Hackers Cloning Websites, Exploiting RCE Flaws To Gain Access To Shopping Platforms

Cybercriminals are leveraging AI-powered phishing attacks, website cloning tools, and RCE exploits to target...

Hackers Exploited Windows Event Logs Tool log Manipulation, And Data Exfiltration

wevtutil.exe, a Windows Event Log management tool, can be abused for LOLBAS attacks. By...

Threat Actors Allegedly Claims Breach of EazyDiner Reservation Platform

Reports have emerged of a potential data breach involving EazyDiner, a leading restaurant reservation...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

ElizaRAT Exploits Google, Telegram, & Slack Services For C2 Communications

APT36, a Pakistani cyber-espionage group, has recently upgraded its arsenal with ElizaRAT, a sophisticated...

New CleverSoar Malware Attacking Windows Users Bypassing Security Mechanisms

CleverSoar, a new malware installer, targets Chinese and Vietnamese users to deploy advanced tools...

Beware Of Malicious PyPI Packages That Inject infostealer Malware

Recent research uncovered a novel crypto-jacking attack targeting the Python Package Index (PyPI), where...