← Back to index
References / filed

WAKE_LOCK

Keeps the CPU awake with the screen off so background work survives, which the polling workers need to finish an upload.

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

Granted automatically at install. WAKE_LOCK lets an app prevent the device entering certain low power states while it works. In practice that means keeping the CPU running so an operation continues even when the screen is off.

The write-up treats it as having a clear legitimate reading and a clear illegitimate one, and settles on "both": it is entirely reasonable for a task needing uninterrupted processing, and equally a way to keep background activity alive far longer than otherwise possible. The manifest analysis moves past it quickly, explicitly declining to explain it in detail as self-explanatory.

That is the correct weight to give it. On its own it takes nothing and stores nothing. Its value to an implant is entirely in combination, which is where it earns its place in the persistence set: RECEIVE_BOOT_COMPLETED gets the implant running again after a reboot, the FOREGROUND_SERVICE types keep it resident against background kills, and this makes sure a specific upload actually finishes while the user is asleep.

An upload that is killed halfway is a data loss the operator cannot recover, so holding a partial wake lock across the POST is a reasonable engineering choice for a criminal client too. The permission is the least interesting one on the list in isolation and one of the load-bearing ones in the set.

Related: FOREGROUND_SERVICE, RECEIVE_BOOT_COMPLETED, REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

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