Allow Android Accessibility Services for Approved Apps
Learn to Use a whitelist in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is the Allow Accessibility with Specified Apps Feature?
The feature Allow Accessibility with Specified Apps enables adding apps to a whitelist, namely: a list of apps that have been approved to enable and use Android AccessibilityService.
What are Android Accessibility Services?
Accessibility Services are OS settings/features in Android that are designed to help users with disabilities (for example: screen readers, speech to text, touch events). These features run in the background and receive callbacks by the system when accessibility events are fired, making them capable of reacting to a state transition in the UI (for example: focus has changed, content in the active window was queried).
These services also typically run with a higher level of administrative privilege, and for this reason, Accessibility Services 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.
Prerequisites for Using Allow Accessibility with Specified Apps:
To use Appdome’s mobile app security build system to Use a whitelist , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Allow Accessibility with Specified Apps
- Mobile App (.apk or .aab for Android)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Use a whitelist on Android apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Android Apps that Use a whitelist without an SDK or gateway:
-
Upload the Mobile App to Appdome.
-
Upload an app to Appdome’s Mobile App Security Build System
-
Upload Method: Appdome Console or DEV-API
-
Android Formats: .apk or .aab
-
Allow Accessibility with Specified Apps Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
-
-
Build the feature: Allow Accessibility with Specified Apps.
-
Building Allow Accessibility with Specified Apps by using Appdome’s DEV-API:
-
Create and name the Fusion Set (security template) that will contain the Allow Accessibility with Specified Apps feature as shown below:
-
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Allow Accessibility with Specified Apps feature via Appdome Console, to add the Allow Accessibility with Specified Apps feature to this Fusion Set.
-
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):
Figure 2: Fusion Set Detail Summary
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory). -
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:
-
Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
-
Look for sample APIs in Appdome’s GitHub Repository
-
Figure 1: Fusion Set that will contain the Allow Accessibility with Specified Apps feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required). -
-
Building the Allow Accessibility with Specified Apps feature via Appdome Console
To build the Allow Accessibility with Specified Apps protection by using Appdome Console, follow the instructions below.
-
Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
-
How: Check whether is toggled On (enabled), otherwise enable it . The feature Allow Accessibility with Specified Apps is enabled by default, as shown below. Toggle (turn ON) Allow Accessibility with Specified Apps, 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 Uses a whitelist.
Figure 3: Use a whitelist 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. -
When you select the Allow Accessibility with Specified Apps you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Allow Accessibility with Specified Apps
Figure 4: Fusion Set that displays the newly added Allow Accessibility with Specified Apps protection
-
Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Allow Accessibility with Specified Apps:
-
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 Use a whitelist.
-
Threat-Events™ ON > In-App Detection
When this setting is used, Appdome detects if malicious apps are running on the device with Accessibility Services permissions enabled 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 Allow Accessibility with Specified Apps Intelligence and Control in Mobile Apps.
-
Threat-Events™ ON > In-App Defense
When this setting is used, Appdome detects and defends against a whitelist (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 Allow Accessibility with Specified Apps Intelligence and Control in Mobile Apps.
-
- Extra Configuration with Allow Accessibility with Specified Apps:
- Allow Accessibility with Specified Apps (optional)
Click on Add then list the bundle IDs of the apps you want to Allow Accessibility Service for
-
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
-
Congratulations! The Allow Accessibility with Specified Apps protection is now added to the mobile app -
-
Certify the Allow Accessibility with Specified Apps feature in Android Apps
After building Allow Accessibility with Specified Apps, Appdome generates a Certified Secure™ certificate to guarantee that the Allow Accessibility with Specified Apps protection has been added and is protecting the app. To verify that the Allow Accessibility with Specified Apps 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 Allow Accessibility with Specified Apps has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Allow Accessibility with Specified Apps and other mobile app security features are in each build of the mobile app
Using Threat-Events™ for a whitelist Intelligence and Control in Android Apps
Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when a whitelist is detected. To consume and use Threat-Events™ for a whitelist in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for a whitelist shown below.
The specifications and options for Threat-Events™ for a whitelist are:
| Threat-Event™ Elements | Use a whitelist Method Detail |
|---|---|
| Appdome Feature Name | Allow Accessibility with Specified Apps |
| 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 Using a whitelist Threat-Event™ | |
| Threat-Event NAME | AccessibilityServiceDetected |
| Threat-Event DATA | reasonData |
| Threat-Event CODE | reasonCode |
| Threat-Event REF | 6801 |
| 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 a whitelist is detected.
The following is a code sample for native Android apps, which uses all values in the specification above for Allow Accessibility with Specified Apps:
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.
xxxxxxxxxx1
20
1
15
1
15
1
15
1
IntentFilter intentFilter = new IntentFilter();2
intentFilter.addAction("AccessibilityServiceDetected");3
BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {4
5
public void onReceive(Context context, Intent intent) {6
String message = intent.getStringExtra("message"); // Message shown to the user7
String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause8
String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code9
10
// Current threat event score11
String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore");12
13
// Total threat events score14
String threatEventsScore = intent.getStringExtra("threatEventsScore");15
16
// Replace '<Context Key>' with your specific event context key17
// String variable = intent.getStringExtra("<Context Key>");18
19
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)20
}21
};22
23
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {24
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);25
} else {26
registerReceiver(threatEventReceiver, intentFilter);27
}xxxxxxxxxx1
20
1
15
1
15
1
15
1
val intentFilter = IntentFilter()2
intentFilter.addAction("AccessibilityServiceDetected")3
val threatEventReceiver = object : BroadcastReceiver() {4
override fun onReceive(context: Context?, intent: Intent?) {5
var message = intent?.getStringExtra("message") // Message shown to the user6
var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause7
var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code8
9
// Current threat event score10
var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore")11
12
// Total threat events score13
var threatEventsScore = intent?.getStringExtra("threatEventsScore")14
15
// Replace '<Context Key>' with your specific event context key16
// var variable = intent?.getStringExtra("<Context Key>")17
18
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)19
}20
}21
22
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {23
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)24
} else {25
registerReceiver(threatEventReceiver, intentFilter)26
}xxxxxxxxxx1
20
1
15
1
15
1
15
2
29
1
const { ADDevEvents } = NativeModules;2
const aDDevEvents = new NativeEventEmitter(ADDevEvents);3
4
function registerToDevEvent(action, callback) {5
NativeModules.ADDevEvents.registerForDevEvent(action);6
aDDevEvents.addListener(action, callback);7
}8
9
export function registerToAllEvents() {10
registerToDevEvent(11
"AccessibilityServiceDetected",12
(userinfo) => Alert.alert(JSON.stringify(userinfo))13
14
var message = userinfo["message"] // Message shown to the user15
var reasonData = userinfo["reasonData"] // Threat detection cause16
var reasonCode = userinfo["reasonCode"] // Event reason code17
18
// Current threat event score19
var currentThreatEventScore = userinfo["currentThreatEventScore"]20
21
// Total threat events score22
var threatEventsScore = userinfo["threatEventsScore"]23
24
// Replace '<Context Key>' with your specific event context key25
// var variable = userinfo["<Context Key>"]26
27
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)28
);29
}x
27
1
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("AccessibilityServiceDetected"));2
3
class ThreatEventReceiver : BroadcastReceiver4
{5
public override void OnReceive(Context context, Intent intent)6
{7
// Message shown to the user8
String message = intent.GetStringExtra("message");9
10
// Threat detection cause11
String reasonData = intent.GetStringExtra("reasonData");12
13
// Event reason code14
String reasonCode = intent.GetStringExtra("reasonCode");15
16
// Current threat event score17
String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore");18
19
// Total threat events score20
String threatEventsScore = intent.GetStringExtra("threatEventsScore");21
22
// Replace '<Context Key>' with your specific event context key23
// String variable = intent.GetStringExtra("<Context Key>");24
25
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)26
}27
}x
1
NSNotificationCenter.DefaultCenter.AddObserver(2
(NSString)"AccessibilityServiceDetected", // Threat-Event Identifier3
delegate (NSNotification notification)4
{5
// Message shown to the user6
var message = notification.UserInfo.ObjectForKey("message");7
8
// Threat detection cause9
var reasonData = notification.UserInfo.ObjectForKey("reasonData");10
11
// Event reason code12
var reasonCode = notification.UserInfo.ObjectForKey("reasonCode");13
14
// Current threat event score15
var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore");16
17
// Total threat events score18
var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore");19
20
// Replace '<Context Key>' with your specific event context key21
// var variable = notification.UserInfo.ObjectForKey("<Context Keys>");22
23
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)24
}25
);xxxxxxxxxx1
20
1
15
1
15
1
15
2
29
1
window.broadcaster.addEventListener("AccessibilityServiceDetected", function(userInfo) {2
var message = userInfo.message // Message shown to the user3
var reasonData = userInfo.reasonData // Threat detection cause4
var reasonCode = userInfo.reasonCode // Event reason code5
6
// Current threat event score7
var currentThreatEventScore = userInfo.currentThreatEventScore8
9
// Total threat events score10
var threatEventsScore = userInfo.threatEventsScore11
12
// Replace '<Context Key>' with your specific event context key13
// var variable = userInfo.<Context Keys>14
15
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)16
});x
1
import 'dart:async';2
import 'package:flutter/material.dart';3
import 'package:flutter/services.dart';4
5
class PlatformChannel extends StatefulWidget {6
const PlatformChannel({super.key});7
8
9
State<PlatformChannel> createState() => _PlatformChannelState();10
}11
12
class _PlatformChannelState extends State<PlatformChannel> {13
// Replace with your EventChannel name14
static const String _eventChannelName = "AccessibilityServiceDetected";15
static const EventChannel _eventChannel = EventChannel(_eventChannelName);16
17
18
void initState() {19
super.initState();20
_eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);21
}22
23
void _onEvent(Object? event) {24
setState(() {25
// Adapt this section based on your specific event data structure26
var eventData = event as Map;27
28
// Example: Accessing 'externalID' field from the event29
var externalID = eventData['externalID'];30
31
// Customize the rest of the fields based on your event structure32
String message = eventData['message']; // Message shown to the user33
String reasonData = eventData['reasonData']; // Threat detection cause34
String reasonCode = eventData['reasonCode']; // Event reason code35
36
// Current threat event score37
String currentThreatEventScore = eventData['currentThreatEventScore'];38
39
// Total threat events score40
String threatEventsScore = eventData['threatEventsScore'];41
42
// Replace '<Context Key>' with your specific event context key43
// String variable = eventData['<Context Keys>'];44
});45
}46
47
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)48
}Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Allow Accessibility with Specified Apps. 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 Allow Accessibility with Specified Apps
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:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
Related Articles:
How to Prevent abuse of Accessibility Service
How to Block Overlay Attacks on Android Apps
How to Prevent Malicious Misuse of Android Debug Bridge (ADB)
Check out the Appdome Mobile Fraud Prevention solution page.
Check out Mobile Fraud Prevention or request a demo at any time.
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.
