Cloaking Accessibility Events from Keyloggers

Last updated May 2, 2024 by Appdome

Learn to Prevent hackers from obtaining Accessibility-related permissions from the user in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are accessibility events?

Accessibility Events are events fired by the Android system when a notable change takes place in the user interface. Firing an event is performed by an Android View, which can fill the event with data about the UI change; for example, when a Button View was clicked or upon a text change in TextView Views.

The purpose of these events is to send notifications about UI changes to applications that use Accessibility Service. The enhanced capabilities of the user interface, which are integrated into the Accessibility Service, are generally meant to help users with disabilities interact with the application.

Why Cloak Accessibility Events?

Accessibility Events enable receiving data about most UI elements displayed on the app, which implemented the Accessibility Service class. Alternatively, these events enable obtaining the same data about other apps running on the device, if the data-receiving app has the appropriate permissions enabled.

By exploiting these the aforementioned capabilities, a potential attacker can disguise a malicious app as a seemingly innocent app. Then, after obtaining the Accessibility-related permissions from the user, the attacker can record View changes – particularly keystrokes – on other apps. In so doing, the attacker can collect highly confidential data items such as passwords and private personal information.

Developers can use this feature to cloak Accessibility Events so that those events cannot be read by attackers, keyloggers or other malware.

Prerequisites for Using Keylogging Prevention > Accessibility Events Cloaking:

To use Appdome’s mobile app security build system to Prevent hackers from obtaining Accessibility-related permissions from the user , you’ll need:

Prevent hackers from obtaining Accessibility-related permissions from the user on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Prevent hackers from obtaining Accessibility-related permissions from the user 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. Keylogging Prevention > Accessibility Events Cloaking Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Keylogging Prevention > Accessibility Events Cloaking.

    1. Building Keylogging Prevention > Accessibility Events Cloaking by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Keylogging Prevention > Accessibility Events Cloaking feature as shown below:
      2. fusion set that contains Keylogging Prevention > Accessibility Events Cloaking

        Figure 1: Fusion Set that will contain the Keylogging Prevention > Accessibility Events Cloaking 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 Keylogging Prevention > Accessibility Events Cloaking feature via Appdome Console, to add the Keylogging Prevention > Accessibility Events Cloaking 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 Keylogging Prevention > Accessibility Events Cloaking feature via Appdome Console

      To build the Keylogging Prevention > Accessibility Events Cloaking protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Secure Communication section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature Keylogging Prevention > Accessibility Events Cloaking is enabled by default, as shown below. Toggle (turn ON) Keylogging Prevention > Accessibility Events Cloaking, as shown below. Keylogging Prevention > Accessibility Events Cloaking option

        Figure 3: Prevent hackers from obtaining Accessibility-related permissions from the user option

      3. When you select the Keylogging Prevention > Accessibility Events Cloaking you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Keylogging Prevention > Accessibility Events Cloaking

        Fusion Set applied Keylogging Prevention > Accessibility Events Cloaking

        Figure 4: Fusion Set that displays the newly added Keylogging Prevention > Accessibility Events Cloaking protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Keylogging Prevention > Accessibility Events Cloaking protection is now added to the mobile app
  3. Certify the Keylogging Prevention > Accessibility Events Cloaking feature in Android Apps

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

Using Threat-Events™ for hackers from obtaining Accessibility-related permissions from the user Intelligence and Control in Android Apps

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

The specifications and options for Threat-Events™ for hackers from obtaining Accessibility-related permissions from the user are:

Threat-Event™ Elements Prevent hackers from obtaining Accessibility-related permissions from the user Method Detail
Appdome Feature Name Keylogging Prevention > Accessibility Events Cloaking
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 Preventing hackers from obtaining Accessibility-related permissions from the user 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 hackers from obtaining Accessibility-related permissions from the user are detected.


The following is a code sample for native Android apps, which uses all values in the specification above for Keylogging Prevention > Accessibility Events Cloaking:


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 Keylogging Prevention > Accessibility Events Cloaking. 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 Keylogging Prevention > Accessibility Events Cloaking

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?

Anti-Spyware Detection

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