Block Shamiko Magisk, Prevent Root Hiding

Last updated January 1, 2024 by Appdome

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

What is Shamiko?

The Shamiko module is a specific modification type designed for Android devices that utilize Magisk or KernelSU. These modifications are packaged as ZIP archives and contain essential files and metadata necessary for its operation. By leveraging Shamiko, hackers can distribute and apply modifications to Android devices, posing a potential risk of exposing devices to malware and unauthorized access. In addition, the Shamiko Module conceals Zygisk/Riru and other modules, enabling users to mask their device’s root status.

Why Block Shamiko in Android Apps?

Shamiko’s ability to distribute and apply modifications can potentially be exploited to alter or manipulate the functionality of apps, which can lead to unauthorized access to premium features, unauthorized distribution of copyrighted content, or other violations of the app’s terms of service. Blocking Shamiko ensures that users access the official, unaltered version of the app, reducing the risk of security breaches, data theft, or fraudulent activities.

Prerequisites for Using Block Shamiko:

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

Block Shamiko on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Block Shamiko 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. Block Shamiko Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Block Shamiko.

    1. Building Block Shamiko by using Appdome’s DEV-API:

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

        Figure 1: Fusion Set that will contain the Block Shamiko 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 Block Shamiko feature via Appdome Console, to add the Block Shamiko 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. Copy 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 Block Shamiko feature via Appdome Console

      To build the Block Shamiko protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature Block Shamiko is enabled by default, as shown below. Toggle (turn ON) Block Shamiko, as shown below. Block Shamiko option

        Figure 3: Block Shamiko option

      3. When you select the Block Shamiko you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Block Shamiko

        Fusion Set applied Block Shamiko

        Figure 4: Fusion Set that displays the newly added Block Shamiko protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Block Shamiko protection is now added to the mobile app
  3. Certify the Block Shamiko feature in Android Apps

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

    Figure 5: 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 Shamiko has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block Shamiko and other mobile app security features are in each build of the mobile app

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

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

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

Threat-Event™ Elements Block Shamiko Method Detail
Appdome Feature Name Block Shamiko
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 Blocking Shamiko 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
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

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


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


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 Shamiko. 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 Shamiko

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.