How to Prevent Static App Patching in Android Apps

Last updated May 26, 2024 by Appdome

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?

If an app is not sufficiently protected against reverse engineering, attackers can take an original app and modify the binary code by adding malicious code to the app and repackaging the app bundle so that the changes are permanent.

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 type of attack and ensures that the original code is preserved and users are protected.

Prerequisites for Using Prevent Static App Patching:

To use Appdome’s mobile app security build system to Prevent Static App Patching , you’ll need:

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:

  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. Prevent Static App Patching Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Prevent Static App Patching.

    1. Building Prevent Static App Patching by using Appdome’s DEV-API:

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

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

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

      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 Prevent Static App Patching feature via Appdome Console

      To build the Prevent Static App Patching protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > ONEShield™ section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature Prevent Static App Patching is enabled by default, as shown below. Toggle (turn ON) Prevent Static App Patching, as shown below. Prevent Static App Patching option

        Figure 3: Prevent Static App Patching option

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

        Fusion Set applied Prevent Static App Patching

        Figure 4: Fusion Set that displays the newly added Prevent Static App Patching protection

      4. 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
  3. 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: Prevent Static App Patching 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 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
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.
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:


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 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:

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?

Mobile RASP Security

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