Block Shamiko Magisk, Prevent Root Hiding

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:

• Appdome account (create a free Appdome account here)

• A license for Block Shamiko & Block Zygisk 

• Mobile App (.apk or .aab For Android)

• Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)

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:
      

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

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

      3. 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):

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

      4. 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, Cirlce 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.

         Like all other options in ONEShield™, Block Shamiko is turned on by default, as shown below:

         Figure 3: Block Shamiko option
         Note: The App Compromise Notification contains an easy to follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand specific support, workflow or other messaging.

      2. How: Toggle (turn ON) Block Shamiko, as shown below.

         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

         

         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:

   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