How to Block Lucky Patcher & Patching Tools in Android Apps

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

What is Lucky Patcher?

Lucky Patcher is a free ‘app modifier’ app used for cheating in Android mobile games. Although there are both root and no-root versions of Lucky Patcher, the more powerful hacking/modding functions require root access or Rooting Android.  On rooted devices, Lucky Patcher enables more powerful functions, such as the ability to bypass in-app purchases, obtain special game powers, disable ads in mobile games, or turn off licensing verification to play premium games for free.

Why Block Lucky Patcher in Android Apps?

Lucky Patcher is harmful to mobile games and game developers for several reasons. For one, gamers/hackers can use Lucky Patcher to bypass license validation and/or disable mobile advertising – the two primary revenue sources for most mobile games. In addition, blocking Lucky Patcher preserves the integrity of the game and prevents attrition from non-cheaters who are frustrated by the growing number of players who use tools like Lucky Patcher to gain advantages at the expense of honest players. Appdome’s Root Detection feature allows app developers to quickly and easily protect apps against Rooting, by blocking apps such as Lucky Patcher that rely on Android rooting and root cloaking in order to enable the more powerful cheating features.

Blocking Lucky Patcher on Android apps by Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Block Lucky Patcher 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

2. Build the feature: Root Detection.

   1. Building Root Detection by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Root Detection feature as shown below:
      

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

      To build the Root Detection protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > OS Integrity section
      2. How: Toggle (turn ON) Root Detection, 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 Lucky Patcher.

         Figure 3: Block Lucky Patcher 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.

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

         

         Figure 4: Fusion Set that displays the newly added Root Detection protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).

   Congratulations!  The Root Detection protection is now added to the mobile app

3. Certify the Root Detection feature in Android Apps.

   After building Root Detection, Appdome generates a Certified Secure™ certificate to guarantee that the Root Detection protection has been added and is protecting the app. To verify that the Root Detection 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 Root Detection has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Root Detection and other mobile app security features are in each build of the mobile app