How to Detect Zygisk and Root Hiding in Android Apps

Last updated September 17, 2024 by Appdome

This Knowledge Base article describes how to use Appdome’s AI/ML in your CI/CD pipeline to continuously deliver plugins that Detect Zygisk in Android apps.

What is Zygisk?

Zygisk is a feature of Magisk that allows advanced module developers to execute code directly in any Android app’s processes before the processes run. In doing so, Zygisk is able to gain root access without sending root data, as it starts first after the system and before the app. This capability makes Zygisk much more powerful than Magisk Hide in terms of hiding the fact that their device is rooted from the end user. As a result, unsuspecting users will run security-related applications, such as banking services, on the manipulated device.

Why Should Developers Block Zygisk?

Zygisk is an extremely powerful and damaging addition to Magisk. By using Zygisk, malicious actors are able to execute code directly in the processes of any Android app before those processes are specialized and executed. Zygisk also allows such actors to have much better, harder to detect root capabilities to hide the operation of Magisk (root cloaking).

Prerequisites for Using Appdome's Block Zygisk Plugins:

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

How to Implement Detect Zygisk in Android Apps Using Appdome

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

  1. Designate the Mobile App to be protected.

    1. Upload an app via the Appdome Mobile Defense platform GUI or via Appdome’s DEV-API or CI/CD Plugins.

    2. Android Formats: .apk or .aab
    3. Block Zygisk is compatible with: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps.
  2. Select the defense: Block Zygisk.

      1. Create and name the Fusion Set (security template) that will contain the Block Zygisk feature as shown below:
        fusion set that contains Block Zygisk .

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

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the Block Zygisk feature to your Fusion Set via the Appdome Console.

      3. When you enable Block Magisk you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Block Zygisk.

        Fusion Set applied Block Zygisk

        Figure 2: Fusion Set that displays the newly added Block Zygisk protection
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 3: Fusion Set Detail Summary

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, Jenkins, Travis, Team City, Circle CI or other system:
        1. Refer to the Appdome API Reference Guide for API building instructions.
        2. Look for sample APIs in Appdome’s GitHub Repository.
    1. Add the Block Zygisk feature to your security template.

      1. Navigate to Build > Anti Fraud tab > Mobile Malware Prevention section in the Appdome Console.
      2. Toggle On Block Magisk > Block Zygisk.
        Note: The checkmark feature Block Zygisk is enabled by default, as shown below.

        (a) Choose to monitor this attack vector by checking the Threat Events checkbox associated with Block Zygisk as shown below.

        (b) To receive mobile Threat Monitoring, check the ThreatScope™ box as shown below. For more details, see our knowledge base article on ThreatScope™ Mobile XDR.
        Block Zygisk option

        Figure 4: Selecting Detect Zygisk

        Note: The Appdome Platform displays the Mobile Operation Systems supported by each defense in real-time. For more details, see our OS Support Policy KB.

      3. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Block Zygisk:
        1. Threat-Events™ OFF > In-App Defense

          If the Threat-Events™ setting is not selected. Appdome will detect and defend the user and app by enforcing Zygisk.

        2. Threat-Events™ ON > In-App Detection

          When this setting is used, Appdome detects Block Magisk and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing, enforcement, and user notification. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ to Block ZygiskDetect Intelligence and Control in Mobile Apps.

        3. Threat-Events™ ON > In-App Defense

          When this setting is used, Appdome detects and defends against Zygisk (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Block ZygiskDetect Intelligence and Control in Mobile Apps.

      4. Configure the User Experience Options for Block Zygisk:
        With Threat-Events™ OFF, Appdome provides several user experience options for mobile brands and developers.
        1. App Compromise Notification: Customize the pop-up or toast Appdome uses to notify the user when a threat is present while using the protected mobile app.
        2. Short message Option. This is available for mobile devices that allow a banner notification for security events.
        3. Localized Message Option. Allows Appdome users to support global languages in security notifications.

          Localized Message

          Figure 5: Default User Experience Options for Appdome’s Zygisk

        4. Block Zygisk Threat Code™. Appdome uses AI/ML to generate a unique code each time Block Zygisk is triggered by an active threat on the mobile device. Use the code in Appdome Threat Resolution Center™ to help end users identify, find and resolve active threats on the personal mobile devices.
    2. Initiate the build command either by clicking Build My App at the bottom of the Build Workflow (shown in Figure 4) or via your CI/CD as described in Section 2.1.4.
    Congratulations!  The Block Zygisk protection is now added to the mobile app
  3. Certify the Block Zygisk feature in Android Apps

    After building Block Zygisk, Appdome generates a Certified Secure™ certificate to guarantee that the Block Zygisk protection has been added and is protecting the app. To verify that the Block Zygisk protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Block Zygisk shown in Certificate secure

    Figure 6: Certified Secure™ certificate

    Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Block Zygisk has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block Zygisk and other mobile app security features are in each build of the mobile app.

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

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

The specifications and options for Threat-Events™ for Zygisk are:

Threat-Event™ Elements Detect Zygisk Method Detail
Appdome Feature Name Block Zygisk
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
Visible in ThreatScope™
Developer Parameters for Detecting Zygisk Threat-Event™
Threat-Event NAME MagiskManagerDetected
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6908
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
failSafeEnforce Timed enforcement against the identified threat
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. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device. Only available for Android.
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
threatCode The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device.
internalError Internal error code as hex
extendedMessageText Internal error code
rInternalErrorCode Internal error code
data The artifcat used to detect the presence of Magisk Manager on the device
detectedAppPath When applicable this will hold the app identifier that triggered the detection

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 Zygisk is detected.


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


Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.



Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Block Zygisk. 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 Block Zygisk

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:

How Do I Learn More?

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?

Android Malware Detection

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

Search Appdome Solutions

Search
Supercharge The Experience In Mobile App Defense

Supercharge the Experience in Mobile App Defense

Appdome revolutionizes mobile app defense by integrating security seamlessly, enhancing the user experience for developers, cyber teams, and end-users without disruption.

Better User Experience In Mobile Defense

Better User Experience in Mobile Defense

This blog show how Appdome’s Intelligent Defense helps mobile brands and users resolve threats with the user experience as a central priority.