What malware persistence mechanism does Android malware use to survive a device reboot without root access?
- A.D) Malware persists by modifying the .apk file at the system partition level; only factory reset removes system-partition modifications.
- B.B) Non-root malware cannot survive device reboots; restarting the phone always removes malware that lacks root access.
- C.C) Android malware uses bootkit techniques to inject code into the init process before the Android runtime starts; this requires exploiting a pre-boot vulnerability.
- D.A) Non-root Android malware persists across reboots by registering a BroadcastReceiver for BOOT_COMPLETED (requires RECEIVE_BOOT_COMPLETED permission) in the manifest; when the device boots, Android fires this broadcast and restarts the malware service. Additionally, a foreground service with startForeground() makes the malware harder for the OS to kill, and WorkManager provides scheduled restart as another fallback.