| ID | Name |
|---|---|
| T1629.001 | Prevent Application Removal |
| T1629.002 | Device Lockout |
| T1629.003 | Disable or Modify Tools |
Adversaries may disable security tools to avoid potential detection of their tools and activities. This can take the form of disabling security software, modifying SELinux configuration, or other methods to interfere with security tools scanning or reporting information. This is typically done by abusing device administrator permissions or using system exploits to gain root access to the device to modify protected system files.
| ID | Name | Description |
|---|---|---|
| S1061 | AbstractEmu |
AbstractEmu can disable Play Protect.[1] |
| S1214 | Android/SpyAgent |
Android/SpyAgent has attempted to detect anti-spam call applications.[2] |
| S0422 | Anubis |
Anubis can modify administrator settings and disable Play Protect.[3] |
| S1094 | BRATA |
BRATA can remove installed antivirus applications as well as disable Google Play Protect.[4][5] |
| C0033 | C0033 |
During C0033, PROMETHIUM used StrongPity to modify permissions on a rooted device and tried to disable the SecurityLogAgent application.[6] |
| S0480 | Cerberus |
Cerberus disables Google Play Protect to prevent its discovery and deletion in the future.[7] |
| S1083 | Chameleon |
Chameleon has the ability to disable Google Play Protect.[8][9] |
| S1054 | Drinik |
Drinik can use Accessibility Services to disable Google Play Protect.[10] |
| S0420 | Dvmap |
Dvmap can turn off |
| S1067 | FluBot |
FluBot can disable Google Play Protect to prevent detection.[12][13] |
| S0485 | Mandrake | |
| S1195 | SpyC23 | |
| S0494 | Zen |
| ID | Mitigation | Description |
|---|---|---|
| M1010 | Deploy Compromised Device Detection Method |
Mobile security software can typically detect if a device has been rooted or jailbroken and can inform the user, who can then take appropriate action. |
| M1001 | Security Updates |
Security updates frequently contain patches to vulnerabilities that can be exploited for root access. |
| M1004 | System Partition Integrity |
System partition integrity mechanisms, such as Verified Boot, can detect the unauthorized modification of system files. |
| M1011 | User Guidance |
Users should be taught the dangers of rooting or jailbreaking their device. |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0693 | Detection of Disable or Modify Tools | AN1806 |
For Android, detect Disable or Modify Tools from documented management, network, or vetting evidence; treat state queries as periodic observations rather than real-time events. Correlate Application Permission via Android Enterprise DPC / Application Vetting [DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review]; File Creation via Application Vetting / Forensic Acquisition [Dynamic filesystem trace or acquired app-container/filesystem artifacts: App writes to or modifies protected configuration files or local control structures of deployed security tools]; OS API Execution via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: App invokes package manager operations (disable component, clear data, request uninstall) or settings modifications targeting security tool packages IN $SecurityToolPackageList$]. Alert on a sequence or state change inconsistent with the device/app baseline, approved management policy, or expected user workflow; do not infer unobserved API calls, file/process activity, or payload content from management state alone. |