An intent is a message passed between Android application or system components. Applications can register to receive broadcast intents at runtime, which are system-wide intents delivered to each app when certain events happen on the device, such as network changes or the user unlocking the screen. Malicious applications can then trigger certain actions within the app based on which broadcast intent was received.
Further, malicious applications can register for intents broadcasted by other applications in addition to the Android system itself. This allows the malware to respond based on actions in other applications. This behavior typically indicates a more intimate knowledge, or potentially the targeting of specific devices, users, or applications.
In Android 8 (API level 26), broadcast intent behavior was changed, limiting the implicit intents that applications can register for in the manifest. In most cases, applications that register through the manifest will no longer receive the broadcasts. Now, applications must register context-specific broadcast receivers while the user is actively using the app.[1]
ID | Name | Description |
---|---|---|
S0525 | Android/AdDisplay.Ashas |
Android/AdDisplay.Ashas has registered to receive the |
S0524 | AndroidOS/MalLocker.B |
AndroidOS/MalLocker.B has registered to receive 14 different broadcast intents for automatically triggering malware payloads. [3] |
S0479 | DEFENSOR ID |
DEFENSOR ID abuses the accessibility service to auto-start the malware on device boot. This is accomplished by receiving the |
S0478 | EventBot |
EventBot registers for the |
S0522 | Exobot |
Exobot has registered to receive the |
S0509 | FakeSpy |
FakeSpy can register for the |
S0408 | FlexiSpy |
FlexiSpy uses root access to establish reboot hooks to re-install the application from |
S0421 | GolfSpy |
GolfSpy registers for the |
S0536 | GPlayed |
GPlayed can register for the |
S0544 | HenBox | |
S0316 | Pegasus for Android |
Pegasus for Android listens for the BOOT_COMPLETED broadcast intent in order to maintain persistence and activate its functionality at device boot time.[12] |
S0419 | SimBad |
SimBad registers for the |
S0324 | SpyDealer |
SpyDealer registers the broadcast receiver to listen for events related to device boot-up.[14] |
S0305 | SpyNote RAT |
SpyNote RAT uses an Android broadcast receiver to automatically start when the device boots.[15] |
S0545 | TERRACOTTA |
TERRACOTTA has registered several broadcast receivers.[16] |
S0558 | Tiktok Pro |
Tiktok Pro has registered for device boot, incoming, and outgoing calls broadcast intents.[17] |
S0427 | TrickMo |
TrickMo registers for the |
ID | Mitigation | Description |
---|---|---|
M1006 | Use Recent OS Version |
In Android 8, broadcast intent behavior was changed, limiting the implicit intents that applications can register for in the manifest.[1] |
Broadcast intent receivers are part of standard OS-level APIs and are therefore typically undetectable to the end user.