How to Block Suspicious Accessibility Services in Android Apps

Last updated December 5, 2023 by Appdome

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

What are Accessibility Services?

Android Accessibility Services enable Android apps to assist individuals with disabilities in overcoming their challenges when using their smartphones. An example of such services is a screen reading utility. Such a utility (app) makes texts accessible to the blind or visually impaired by providing talking feedback in response to user manipulations and gestures such as swiping, dragging, or using an external keyboard.

When users download these apps, they need to enable Accessibility Permissions in order to take advantage of these benefits.

Why are Accessibility Services Potentially Dangerous?

Accessibility Services run in the background and receive callbacks by the system when accessibility events such as clicking a button or changing a focus are fired. In response to a callback, an accessibility service can request the capability required for querying the content of the active window.

These services also typically run with a higher level of administrative privilege. For this reason, AccessibilityServices are often used for different purposes for which they were not intended and targeted by hackers to exploit. When abused, they are used to perform click actions (either to commit click-fraud or to cheat in mobile games), read and write SMS messages and emails, intercept and read Two-Factor Authentication codes, steal cryptocurrency keys, control mobile devices or apps remotely and more. In addition, when an app is allowed to take full control over a user’s device, this can result in allowing malware to access the device and take control over it. The presence of malware on a device can eventually lead to the stealing of sensitive information such as personally identifiable information (PII), login credentials, banking/financial data and more. This is done by performing attacks such as key logging, keystroke injection, eavesdropping and more by banking Trojans that work by stealing banking credentials from users.

The Block Suspicious Accessibility Services feature, which is part of the Anti Remote Desktop Control protection, detects and blocks accessibility services that are deemed to be suspicious or malicious.

Prerequisites for Using Block Suspicious Accessibility Services:

To use Appdome’s mobile app security build system to Block Suspicious Accessibility Services , you’ll need:

Block Suspicious Accessibility Services on Android apps using Appdome

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

    1. Building Block Suspicious Accessibility Services by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Block Suspicious Accessibility Services feature as shown below:
      2. fusion set that contains Block Suspicious Accessibility Services

        Figure 1: Fusion Set that will contain the Block Suspicious Accessibility Services 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 Block Suspicious Accessibility Services feature via Appdome Console, to add the Block Suspicious Accessibility Services 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, as shown in Figure 1 above, and get 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 Block Suspicious Accessibility Services feature via Appdome Console

      To build the Block Suspicious Accessibility Services protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
      2. When you select the Block Suspicious Accessibility Services 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 Suspicious Accessibility Services

        Fusion Set applied Block Suspicious Accessibility Services

        Figure 4: Fusion Set that displays the newly added Block Suspicious Accessibility Services protection

      3. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Block Suspicious Accessibility Services:
        1. 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 Suspicious Accessibility Services.

        2. Threat-Events™ ON > In-App Detection

          When this setting is used, Appdome detects the existence of suspicious accessibility services 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 Suspicious Accessibility Services Intelligence and Control in Mobile Apps.

        3. Threat-Events™ ON > In-App Defense

          When this setting is used, Appdome detects and defends against Suspicious Accessibility Services (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 Suspicious Accessibility Services Intelligence and Control in Mobile Apps.

      4. Extra Configuration with Block Suspicious Accessibility Services:
        1. App Compromise Notification

          The message that will be shown to the user when the event is detected. The app will automatically exit.

        2. Localized Messages

          Upload file CSV or JSON for the localized compromise notification message. Key/left column locale e.g. en_US, Value/right column the localized message.

      5. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Block Suspicious Accessibility Services protection is now added to the mobile app

Using Threat-Events™ for Suspicious Accessibility Services Intelligence and Control in Android Apps

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

The specifications and options for Threat-Events™ for Suspicious Accessibility Services are:

Threat-Event™ Elements Block Suspicious Accessibility Services Method Detail
Appdome Feature Name Block Suspicious Accessibility Services
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 Suspicious Accessibility Services Threat-Event™
Threat-Event NAME IllegalAccessibilityServiceEvent
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6801
Threat-Event SCORE
Remote desktop accessibility service serviceName
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 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 Suspicious Accessibility Services are detected.

The following is a code sample for native Android apps, which uses all values in the specification above for Block Suspicious Accessibility Services:


Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Block Suspicious Accessibility Services. 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 Suspicious Accessibility Services

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:

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?

Android Malware Detection

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