How to Disallow Non-System Overlays in Android Apps

Last updated August 14, 2024 by Appdome

Learn to Disallow Non-System Overlays in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are Non-System Overlays?

Non-system overlays are graphical elements or UI components drawn over the main application window by third-party apps. Examples include chat heads, floating buttons, screen filters, and custom keyboards. These overlays add functionality; however, they can also create security risks and disrupt the user experience.

How Does Disallowing Non-System Overlays Protect Your Mobile App?

Disallowing non-system overlays ensures that only system-level overlays, essential for your app’s core functionality, are allowed. This prevents third-party app overlays, which are often unnecessary and can introduce security risks. By blocking these overlays, you safeguard your app from potential overlay attacks that can obscure your interface and create vulnerabilities.

Benefits of Disallowing Non-System Overlays

  • Enhanced Security: Protects against malicious overlays that can intercept user input or display misleading information.
  • Improved User Experience: Prevents third-party overlays from interfering with your app’s interface, ensuring a seamless user experience.
  • Regulatory Compliance: Helps meet security standards and regulations by minimizing the risk of overlay attacks.

API Level for Removing Non-System Overlay

Blocking Non-System Overlays is only supported on devices with Android 12 (API level 31) or newer versions.

Appdome Detection Mechanism

Appdome detects and reports non-system overlays using a partial overlay detection method:

  • If the detection field ‘reason’ equals ‘partialOverlayDetectionMethod,’ Appdome adds a detection field called ‘disallowing_non_system_overlays.’
  • When disallowing_non_system_overlays is set to true, Appdome hides the non-system partial overlays.
  • When disallowing_non_system_overlays is set to false, Appdome does not hide the non-system partial overlays.

Prerequisites for Using Disallow Non-System Overlays:

To use Appdome’s mobile app security build system to Disallow Non-System Overlays , you’ll need:

Disallow Non-System Overlays on Android apps using Appdome

On Appdome, follow these simple steps to create self-defending Android Apps that Disallow Non-System Overlays 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. Disallow Non-System Overlays Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Disallow Non-System Overlays.

    1. Building Disallow Non-System Overlays by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Disallow Non-System Overlays feature as shown below:
      2. fusion set that contains Disallow Non-System Overlays

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

      To build the Disallow Non-System Overlays protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Fraud Detection section.
      2. How: Check whether Block Partial Overlays is toggled On (enabled), otherwise enable it . The feature Disallow Non-System Overlays is enabled by default, as shown below. Toggle (turn ON) Disallow Non-System Overlays, as shown below. Disallow Non-System Overlays option

        Figure 3: Disallow Non-System Overlays option

      3. When you enable Block Partial Overlays you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Disallow Non-System Overlays

        Fusion Set applied Disallow Non-System Overlays

        Figure 4: Fusion Set that displays the newly added Disallow Non-System Overlays protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Disallow Non-System Overlays protection is now added to the mobile app
  3. Certify the Disallow Non-System Overlays feature in Android Apps

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

Using Threat-Events™ for Non-System Overlays Intelligence and Control in Android Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Non-System Overlays is detected. To consume and use Threat-Events™ for Non-System Overlays in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for Non-System Overlays shown below.

The specifications and options for Threat-Events™ for Non-System Overlays are:

Threat-Event™ Elements Disallow Non-System Overlays Method Detail
Appdome Feature Name Disallow Non-System Overlays
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 x
Visible in ThreatScope™ x
Developer Parameters for Disallowing Non-System Overlays Threat-Event™
Threat-Event NAME
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF
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

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 Non-System Overlays is detected.


The following is a code sample for native Android apps, which uses all values in the specification above for Disallow Non-System Overlays:


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 Disallow Non-System Overlays. 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 Disallow Non-System Overlays

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 to Block Partial Overlays in Android Apps

How to Protect Android Apps from Overlay Attacks & Malware

How to Protect Android & iOS Apps from Keylogging Attacks

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?

Anti-Spyware Detection

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