Skip to content

T1626.001 Device Administrator Permissions

Adversaries may abuse Android’s device administration API to obtain a higher degree of control over the device. By abusing the API, adversaries can perform several nefarious actions, such as resetting the device’s password for Endpoint Denial of Service, factory resetting the device for File Deletion and to delete any traces of the malware, disabling all the device’s cameras, or to make it more difficult to uninstall the app.

Device administrators must be approved by the user at runtime, with a system popup showing which actions have been requested by the app. In conjunction with other techniques, such as Input Injection, an app can programmatically grant itself administrator permissions without any user input.

Item Value
ID T1626.001
Sub-techniques T1626.001
Tactics TA0029
Platforms Android
Version 1.1
Created 01 April 2022
Last Modified 20 March 2023

Procedure Examples

ID Name Description
S1061 AbstractEmu AbstractEmu can modify system settings to give itself device administrator privileges.6
S0540 Asacub Asacub can request device administrator permissions.4
S0522 Exobot Exobot can request device administrator permissions.7
S0536 GPlayed GPlayed can request device administrator permissions.8
S0317 Marcher Marcher requests Android Device Administrator access.2
S0539 Red Alert 2.0 Red Alert 2.0 can request device administrator permissions.3
S0318 XLoader for Android XLoader for Android requests Android Device Administrator access.5


ID Mitigation Description
M1006 Use Recent OS Version Changes were introduced in Android 7 to make abuse of device administrator permissions more difficult.1
M1011 User Guidance Users should scrutinize every device administration permission request. If the request is not expected or the user does not recognize the application, the application should be uninstalled immediately.


ID Data Source Data Component
DS0041 Application Vetting Permissions Requests
DS0042 User Interface Permissions Request