How to Block Magisk & Magisk Root in Android Apps
Learn to Block Magisk, Magisk Manager, Zygisk and other Magisk modules in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Magisk, Magisk Manager, Zygisk and other Magisk modules?
Magisk is a “systemless” Rooting tool that is used for elevating privileges to gain system-level access (root access) to the Android OS and underlying file system. Magisk does not make changes to the Android bootloader or require flashing custom ROM. Instead, it stores modifications in the boot partition rather than modify the real system files. Since the original system files remain unchanged, modifications can go undetected by Google SafetyNet and most root detection methods, which makes Magisk Manager an incredibly powerful and popular tool for compromising Android apps.
Magisk Manager is a rooting framework (like its predecessors SuperuserSU and Xposed) that provides multiple modules that enable different rooting features that exploit root access privileges in different ways.
Why Block Magisk, Magisk Manager, Zygisk and other Magisk modules in Android Apps?
All you need to do is have a short read of some of the posts from Magisk creator “topjohnwu” on this and many other threads to understand that Magisk is NOT a tool that you should take lightly. Bottom line, if someone other than the app developer is using Magisk on a rooted Android device that your app is also running on, your app is highly vulnerable to attack unless you have protections built into the app.
Using Appdome, you can block Magisk, Magisk Manager, and Magisk Hide, Zygisk and all other modules and variants of Magisk to protect mobile apps from being compromised by cybercriminals using the Magisk framework.
In addition, Appdome can also Detect Advanced Malware Controls to identify advanced Magisk hiding techniques such as socket and module hiding.
Appdome Anti-Reversing protection along with Anti-Tampering and Anti-Debugging defend any mobile app against tampering, malicious debugging. and reverse engineering, acting as a solid first line of defense. Appdome’s Block Magisk Manager is designed to complement, reinforce, and build upon these other features and defend against experienced cybercriminals using specialized tools.
Prerequisites for Using Block Magisk:
To use Appdome’s mobile app security build system to Block Magisk, Magisk Manager, Zygisk and other Magisk modules , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Block Magisk
- Mobile App (.apk or .aab for Android)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Block Magisk, Magisk Manager, Zygisk and other Magisk modules on Android apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Android Apps that Block Magisk, Magisk Manager, Zygisk and other Magisk modules without an SDK or gateway:
-
Upload the Mobile App to Appdome.
-
Upload an app to Appdome’s Mobile App Security Build System
-
Upload Method: Appdome Console or DEV-API
-
Android Formats: .apk or .aab
-
Block Magisk Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
-
-
Build the feature: Block Magisk.
-
Building Block Magisk by using Appdome’s DEV-API:
-
Create and name the Fusion Set (security template) that will contain the Block Magisk feature as shown below:
-
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Block Magisk feature via Appdome Console, to add the Block Magisk feature to this Fusion Set.
-
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):
Figure 2: Fusion Set Detail Summary
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory). -
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:
-
Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
-
Look for sample APIs in Appdome’s GitHub Repository
-
Figure 1: Fusion Set that will contain the Block Magisk feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required). -
-
Building the Block Magisk feature via Appdome Console
To build the Block Magisk protection by using Appdome Console, follow the instructions below.
-
Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
-
How: Check whether is toggled On (enabled), otherwise enable it . The feature Block Magisk is enabled by default, as shown below. Toggle (turn ON) Block Magisk, as shown below.
If needed, Customize the Threat Notification to be displayed to the mobile end-user in a standard OS dialog notification when Appdome Blocks Magisk, Magisk Manager, Zygisk and other Magisk modules.Figure 3: Block Magisk, Magisk Manager, Zygisk and other Magisk modules 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. -
When you select the Block Magisk 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 Magisk
Figure 4: Fusion Set that displays the newly added Block Magisk protection
-
Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Block Magisk:
-
Threat-Events™ OFF > In-App Defense
If the Threat-Events™ setting is cleared (not selected). Appdome will detect and defend the user and app by enforcing Block Magisk, Magisk Manager, Zygisk and other Magisk modules.
-
Threat-Events™ ON > In-App Detection
When this setting is used, Appdome detects Magisk manager, Zygist or other Magisk modules 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™ for Block Magisk Intelligence and Control in Mobile Apps.
-
Threat-Events™ ON > In-App Defense
When this setting is used, Appdome detects and defends against Magisk, Magisk Manager, Zygisk and other Magisk modules (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence 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 Magisk Intelligence and Control in Mobile Apps.
-
-
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
-
Congratulations! The Block Magisk protection is now added to the mobile app -
-
Certify the Block Magisk feature in Android Apps
After building Block Magisk, Appdome generates a Certified Secure™ certificate to guarantee that the Block Magisk protection has been added and is protecting the app. To verify that the Block Magisk 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 Magisk has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block Magisk and other mobile app security features are in each build of the mobile app
Using Threat-Events™ for Magisk, Magisk Manager, Zygisk and other Magisk modules Intelligence and Control in Android Apps
Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Magisk, Magisk Manager, Zygisk and other Magisk modules is detected. To consume and use Threat-Events™ for Magisk, Magisk Manager, Zygisk and other Magisk modules in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for Magisk, Magisk Manager, Zygisk and other Magisk modules shown below.
The specifications and options for Threat-Events™ for Magisk, Magisk Manager, Zygisk and other Magisk modules are:
Threat-Event™ Elements | Block Magisk, Magisk Manager, Zygisk and other Magisk modules Method Detail |
---|---|
Appdome Feature Name | Block Magisk |
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 Blocking Magisk, Magisk Manager, Zygisk and other Magisk modules 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 |
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 Magisk, Magisk Manager, Zygisk and other Magisk modules is detected.
The following is a code sample for native Android apps, which uses all values in the specification above for Block Magisk:
x
IntentFilter intentFilter = new IntentFilter();
intentFilter.addAction("MagiskManagerDetected");
BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {
public void onReceive(Context context, Intent intent) {
String message = intent.getStringExtra("message"); // Message shown to the user
String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause
String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code
String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore"); // Current threat event score
String threatEventsScore = intent.getStringExtra("threatEventsScore"); // Total threat events score
String variable = intent.getStringExtra("<Context Key>"); // Any other event specific context key
​
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
};
​
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);
} else {
registerReceiver(threatEventReceiver, intentFilter);
}
x
val intentFilter = IntentFilter()
intentFilter.addAction("MagiskManagerDetected")
val threatEventReceiver = object : BroadcastReceiver() {
override fun onReceive(context: Context?, intent: Intent?) {
var message = intent?.getStringExtra("message") // Message shown to the user
var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause
var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code
var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore") // Current threat event score
var threatEventsScore = intent?.getStringExtra("threatEventsScore") // Total threat events score
var variable = intent?.getStringExtra("<Context Key>") // Any other event specific context key
​
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
}
​
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)
} else {
registerReceiver(threatEventReceiver, intentFilter)
}
const { ADDevEvents } = NativeModules;
const aDDevEvents = new NativeEventEmitter(ADDevEvents);
function registerToDevEvent(action, callback) {
NativeModules.ADDevEvents.registerForDevEvent(action);
aDDevEvents.addListener(action, callback);
}
export function registerToAllEvents() {
registerToDevEvent(
"MagiskManagerDetected",
(userinfo) => Alert.alert(JSON.stringify(userinfo))
var message = userinfo["message"] // Message shown to the user
var reasonData = userinfo["reasonData"] // Threat detection cause
var reasonCode = userinfo["reasonCode"] // Event reason code
var currentThreatEventScore = userinfo["currentThreatEventScore"] // Current threat event score
var threatEventsScore = userinfo["threatEventsScore"] // Total threat events score
var variable = userinfo["<Context Key>"] // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
);
}
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("MagiskManagerDetected"));
class ThreatEventReceiver : BroadcastReceiver
{
public override void OnReceive(Context context, Intent intent)
{
String message = intent.GetStringExtra("message"); // Message shown to the user
String reasonData = intent.GetStringExtra("reasonData"); // Threat detection cause
String reasonCode = intent.GetStringExtra("reasonCode"); // Event reason code
String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore"); // Current threat event score
String threatEventsScore = intent.GetStringExtra("threatEventsScore"); // Total threat events score
String variable = intent.GetStringExtra("<Context Key>"); // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
}
NSNotificationCenter.DefaultCenter.AddObserver(
(NSString)"MagiskManagerDetected", // Threat-Event Identifier
delegate (NSNotification notification)
{
var message = notification.UserInfo.ObjectForKey("message"); // Message shown to the user
var reasonData = notification.UserInfo.ObjectForKey("reasonData"); // Threat detection cause
var reasonCode = notification.UserInfo.ObjectForKey("reasonCode"); // Event reason code
var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore"); // Current threat event score
var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore"); // Total threat events score
var variable = notification.UserInfo.ObjectForKey("<Context Keys>"); // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
window.broadcaster.addEventListener("MagiskManagerDetected", function(userInfo) {
var message = userInfo.message // Message shown to the user
var reasonData = userInfo.reasonData // Threat detection cause
var reasonCode = userInfo.reasonCode // Event reason code
var currentThreatEventScore = userInfo.currentThreatEventScore // Current threat event score
var threatEventsScore = userInfo.threatEventsScore // Total threat events score
var variable = userInfo.<Context Key> // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
xxxxxxxxxx
import 'dart:async';
​
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
​
class PlatformChannel extends StatefulWidget {
const PlatformChannel({super.key});
​
State<PlatformChannel> createState() => _PlatformChannelState();
}
​
class _PlatformChannelState extends State<PlatformChannel> {
static const String _eventChannelName = 'MagiskManagerDetected'; // Replace with your EventChannel name
static const EventChannel _eventChannel = EventChannel(_eventChannelName);
​
void initState() {
super.initState();
_eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);
}
​
void _onEvent(Object? event) {
setState(() {
// Adapt this section based on your specific event data structure
var eventData = event as Map;
​
// Example: Accessing 'externalID' field from the event
var externalID = eventData['externalID'];
​
// Customize the rest of the fields based on your event structure
String message = eventData['message']; // Message shown to the user
String reasonData = eventData['reasonData']; // Threat detection cause
String reasonCode = eventData['reasonCode']; // Event reason code
String currentThreatEventScore = eventData['currentThreatEventScore']; // Current threat event score
String threatEventsScore = eventData['threatEventsScore']; // Total threat events score
​
// Any other event specific context key
String variable = eventData['<Context Key>'];
});
}
​
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Block Magisk. 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 Magisk
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:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
Related Articles:
- How to Prevent Rooting Android
- How to Prevent Jailbreaking iOS
- How to Prevent Malicious Misuse of Android Debug Bridge (ADB)
- How to Prevent Malicious use of Frida
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.