| ID | Name |
|---|---|
| T1624.001 | Broadcast Receivers |
Adversaries may establish persistence using system mechanisms that trigger execution based on specific events. Mobile operating systems have means to subscribe to events such as receiving an SMS message, device boot completion, or other device activities.
Adversaries may abuse these mechanisms as a means of maintaining persistent access to a victim via automatically and repeatedly executing malicious code. After gaining access to a victim’s system, adversaries may create or modify event triggers to point to malicious content that will be executed whenever the event trigger is invoked.
| ID | Name | Description |
|---|---|---|
| S1079 | BOULDSPY |
BOULDSPY uses a background service that can restart itself when the parent activity is stopped.[1] |
| S1231 | GodFather |
GodFather has executed when victims utilize their trusted banking apps, as the malware redirects the victim to using a malicious version of the banking app.[2] |
| ID | Mitigation | Description |
|---|---|---|
| M1006 | Use Recent OS Version |
Android 8 introduced additional limitations on the implicit intents that an application can register for.[3] |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0647 | Detection of Event Triggered Execution | AN1727 |
Application vetting services can detect which broadcast intents an application registers for and which permissions it requests. |