AndroidBot malware with obfuscation and multiple capabilities spreading in the wild


SonicWall Threats Research team observed an AndroidBot malware that contains multiple obfuscation layers that hides the hardcoded URLs and malicious code. Similar to a number of Android malware, this malware drops the dex file during execution that contains malicious code.

Sample details

At the time of writing this blog, this sample is hosted on the following link:

Infection Cycle

The app requests for a number of permissions, below are a few risky ones:

  • android.permission.CALL_PHONE
  • android.permission.CAPTURE_VIDEO_OUTPUT
  • android.permission.DISABLE_KEYGUARD
  • android.permission.READ_CONTACTS
  • android.permission.READ_SMS
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.RECEIVE_SMS
  • android.permission.REORDER_TASKS
  • android.permission.REQUEST_DELETE_PACKAGES
  • android.permission.REQUEST_INSTALL_PACKAGES
  • android.permission.SEND_SMS
  • android.permission.SYSTEM_ALERT_WINDOW
  • android.permission.WRITE_EXTERNAL_STORAGE
  • android.permission.WRITE_SMS


Upon installation and execution the application requests for accessibility permissions, once granted the application gains the ability to execute its malicious components:


The main class listed in the Manifest.xml file is not present in the decompiled codebase:


The malware drops a file – agAzJPYW.dex – during execution which is actually the dex file that contains malicious code.:


This dex file contains the main activity which is listed in the original manifest.xml file:


The malware obfuscates the strings present in the code to deter security researchers from analyzing the malware and automated tools from identifying suspicious strings in the code:


However, the decryption routine is also present in the code which can be used to decode the strings:


Decoded string:


We identified several interesting bits when the strings were decoded:





This bot is capable of performing a series of malicious/dangerous actions on an infected device, some of them include:

  • Show custom notifications
  • Screencast/screencapture
  • TeamViewer execution
  • Read, write and send messages
  • Extract information about running processes
  • Extract information about the device
  • Load URLs
  • Receive messages via Fire Cloud Messaging (FCM)
  • Install and remove applications
  • Subscribe to premium messaging services
  • Check if emulator is present


Hardcoded URLs

The class BotConfigs contained an interesting string titled Admin URL. Upon deobfuscation we got the string – http://das37rwa5cyfkb7o.onion/api/mirrors. After a series of layers we ultimately obtained a login page on the link


Based on the hardcoded url’s obtained in the code we created a VirusTotal Graph as shown below:


SonicWall Capture Labs provides protection against this threat via the following signature:

  • AndroidOS.AndroidBot.DX


Indicators of Compromise (IOC):


We have blacklisted the following URLs:



Security News
The SonicWall Capture Labs Threat Research Team gathers, analyzes and vets cross-vector threat information from the SonicWall Capture Threat network, consisting of global devices and resources, including more than 1 million security sensors in nearly 200 countries and territories. The research team identifies, analyzes, and mitigates critical vulnerabilities and malware daily through in-depth research, which drives protection for all SonicWall customers. In addition to safeguarding networks globally, the research team supports the larger threat intelligence community by releasing weekly deep technical analyses of the most critical threats to small businesses, providing critical knowledge that defenders need to protect their networks.