How to Detect SU Binaries on Android Apps

Last updated December 6, 2023 by Appdome

Learn to Detect SU Binaries in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are SU Binaries?

SU Binaries, also referred to as “SuperUser” or simply “SU”, are a key component of Android root access. When an Android device is “rooted,” the user obtains enhanced (super user) permissions, allowing them to modify or access system components that would otherwise be restricted. These elevated permissions are made possible by the SU binary.

Why Detect SU Binaries in Android Apps?

If an Android device has root access, it can bypass system security mechanisms, alter system settings, remove or modify system apps, and install malicious software without the user’s knowledge. This can expose the user’s private data and render the device vulnerable to a wide range of attacks such as memory dumping, debugging, stealing of data and much more. Detecting SU binaries ensures that apps function as intended and that the user data remains secure.

Prerequisites for Using Detect SU Binaries :

To use Appdome’s mobile app security build system to Detect SU Binaries , you’ll need:

Detect SU Binaries on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Detect SU Binaries without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Android Formats: .apk or .aab
    4. Detect SU Binaries Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Detect SU Binaries .

    1. Building Detect SU Binaries by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Detect SU Binaries feature as shown below:
      2. fusion set that contains Detect SU Binaries

        Figure 1: Fusion Set that will contain the Detect SU Binaries feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Detect SU Binaries feature via Appdome Console, to add the Detect SU Binaries feature to this Fusion Set.

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Circle CI or other system:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the Detect SU Binaries feature via Appdome Console

      To build the Detect SU Binaries protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > OS Integrity section.
      2. When you select the Detect SU Binaries you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Detect SU Binaries

        Fusion Set applied Detect SU Binaries

        Figure 4: Fusion Set that displays the newly added Detect SU Binaries protection

      3. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Detect SU Binaries protection is now added to the mobile app

Using Threat-Events™ for SU Binaries Intelligence and Control in Android Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when SU Binaries is detected. To consume and use Threat-Events™ for SU Binaries in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for SU Binaries shown below.

The specifications and options for Threat-Events™ for SU Binaries are:

Threat-Event™ Elements Detect SU Binaries Method Detail
Appdome Feature Name Detect SU Binaries
Threat-Event Mode
OFF, IN-APP DEFENSE Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging.
ON, IN-APP DETECTION Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce).
ON, IN-APP DEFENSE Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection).
Certified Secure™ Threat Event Check x
Visible in ThreatScope™ x
Developer Parameters for Detecting SU Binaries Threat-Event™
Threat-Event NAME
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF
Threat-Event SCORE
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
message Message displayed for the user on event
externalID The external ID of the event which can be listened via Threat Events
osVersion OS version of the current device
deviceModel Current device model
deviceManufacturer The manufacturer of the current device
fusedAppToken The task ID of the Appdome fusion of the currently running app
kernelInfo Info about the kernel: system name, node name, release, version and machine.
carrierPlmn PLMN of the device
deviceID Current device ID
reasonCode Reason code of the occured event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device
updatedOSVersion Is the OS version up to date
deviceBrand Brand of the device
deviceBoard Board of the device
buildUser Build user
buildHost Build host
sdkVersion Sdk version
timeZone Time zone
deviceFaceDown Is the device face down
locationLong Location longitude conditioned by location permission
locationLat Location latitude conditioned by location permission
locationState Location state conditioned by location permission
wifiSsid Wifi SSID
wifiSsidPermissionStatus Wifi SSID permission status

With Threat-Events™ enabled (turned ON), Android developers can get detailed attack intelligence and granular defense control in Android applications and create amazing user experiences for all mobile end users when SU Binaries is detected.

The following is a code sample for native Android apps, which uses all values in the specification above for Detect SU Binaries :


Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Detect SU Binaries . There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with Detect SU Binaries

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

Related Articles:

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

Want a Demo?

Jailbreak & Root Detection

TomWe're here to help
We'll get back to you in 24 hours to schedule your demo.