← Back to index
References / filed

RECEIVE_BOOT_COMPLETED

Runs code at every boot. Here it is one of four registered triggers, so the implant comes back after a reboot without the victim opening it.

255 words2 min read
Filed under
#android#permissions#reference

Granted automatically at install. RECEIVE_BOOT_COMPLETED lets an app receive the boot broadcast and arrange for its components to start automatically after a reboot, rather than waiting for the user to launch it.

The manifest analysis treats it as straightforward persistence, then the code shows how thoroughly it was done. The payload registers not one trigger but four: BOOT_COMPLETED itself, LOCKED_BOOT_COMPLETED which fires before the first unlock and is paired with directBootAware, MY_PACKAGE_REPLACED so the app re-registers after it updates itself, and QUICKBOOT_POWERON plus an HTC vendor variant at com.htc.intent.action.QUICKBOOT-POWERON.

That last detail is the interesting one. An HTC-specific broadcast string is not something a template produces by accident; it is deliberate device coverage for a manufacturer that shipped a non-standard quick-boot action. MY_PACKAGE_REPLACED closes the other loop, since an implant that replaces itself would otherwise lose its receivers.

It belongs with the rest of the persistence set. WAKE_LOCK and the exact-alarm permissions keep work running between reboots, and REQUEST_IGNORE_BATTERY_OPTIMIZATIONS keeps it from being culled by Doze. None of them take anything from the device on their own; together they make sure the implant is still there when the victim picks the phone up again.

Related: WAKE_LOCK, SCHEDULE_EXACT_ALARM, REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.