How to Prevent Static App Patching in Android Apps
Learn to Prevent Static App Patching in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Static App Patching?
Attackers can take original app and modify its code to make the app vulnerable to Rooted devices, debuggers, Frida, and Static Tampering. Malicious code can also be added to the app.
Why Prevent Static App Patching in Android Apps?
The prevention of Static App Patching is one of Anti-Tampering features of Appdome’s ONEShield™. This feature ensures that the app has not been tampered with and does not contain malicious elements.
Using this feature prevents this angle of attack and ensures that the users are protected and that the original code is retained.
Prerequisites to Using Prevent Static App Patching:
To use Appdome’s mobile app security build system to Prevent Static App Patching , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Prevent Static App Patching
- Mobile App (.apk or .aab For Android)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Prevent Static App Patching on Android apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Android Apps that Prevent Static App Patching 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
-
Prevent Static App Patching Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
-
-
Build the feature: Prevent Static App Patching.
-
Building Prevent Static App Patching by using Appdome’s DEV-API:
-
Create and name the Fusion Set (security template) that will contain the Prevent Static App Patching feature as shown below:
-
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Prevent Static App Patching feature via Appdome Console, to add the Prevent Static App Patching feature to this Fusion Set.
-
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). -
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:
-
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 Prevent Static App Patching feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required). -
-
Building the Prevent Static App Patching feature via Appdome Console
To build the Prevent Static App Patching protection by using Appdome Console, follow the instructions below.
-
Where: Inside the Appdome Console, go to Build > Security Tab > ONEShield™ section . Like all other options in ONEShield™, Prevent Static App Patching is turned on by default, as shown below:
Figure 3: Prevent Static App Patching 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 Prevent Static App Patching you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Prevent Static App Patching
Figure 4: Fusion Set that displays the newly added Prevent Static App Patching protection
-
Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Prevent Static App Patching:
-
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 Prevent Static App Patching.
-
Threat-Events™ ON > In-App Detection
When this setting is used, Appdome detects app code has been changed 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 Prevent Static App Patching Intelligence and Control in Mobile Apps.
-
Threat-Events™ ON > In-App Defense
When this setting is used, Appdome detects and defends against Static App Patching (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 Prevent Static App Patching Intelligence and Control in Mobile Apps.
-
-
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
-
Congratulations! The Prevent Static App Patching protection is now added to the mobile app -
-
Certify the Prevent Static App Patching feature in Android Apps.
After building Prevent Static App Patching, Appdome generates a Certified Secure™ certificate to guarantee that the Prevent Static App Patching protection has been added and is protecting the app. To verify that the Prevent Static App Patching 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 Prevent Static App Patching has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Prevent Static App Patching and other mobile app security features are in each build of the mobile app
Using Threat-Events™ for Static App Patching Intelligence and Control in Android Apps
Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Static App Patching is detected. To consume and use Threat-Events™ for Static App Patching in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for Static App Patching shown below.
The specifications and options for Threat-Events™ for Static App Patching are:
Threat-Event™ Elements | Prevent Static App Patching Method Detail |
---|---|
Appdome Feature Name | Prevent Static App Patching |
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 Preventing Static App Patching Threat-Event™ | |
Threat-Event NAME | AppIntegrityError |
Threat-Event DATA | reasonData |
Threat-Event CODE | reasonCode |
Threat-Event REF | 6917 |
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 long |
locationLat | Location lat |
locationState | Location state |
wifiSsid | Wifi SSID |
wifiSsidPermissionStatus | Wifi SSID permission status |
AntampIntegrityErrorMessage | Error message |
data | Data related to the security event |
certificateSHA1 | Failed certificate |
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 Static App Patching is detected.
The following is a code sample for native Android apps, which uses all values in the specification above for Prevent Static App Patching:
x
IntentFilter intentFilter = new IntentFilter();
intentFilter.addAction("AppIntegrityError");
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("AppIntegrityError")
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(
"AppIntegrityError",
(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("AppIntegrityError"));
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)"AppIntegrityError", // 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("AppIntegrityError", 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...)
});
Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Prevent Static App Patching. 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 Prevent Static App Patching
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.
All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.
Related Articles:
- How to Prevent Running on Simulators in Android & IOS Apps
- ONEShield™ No-Code Mobile RASP Explained
- How to Prevent Android Apps from Running on Emulators
- Running a Checksum Validation of Android & iOS Apps
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.