REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
Asks the victim to exempt the app from Doze and App Standby, so the upload workers are not culled while they exfiltrate.
This one is a request rather than a grant. REQUEST_IGNORE_BATTERY_OPTIMIZATIONS lets an app ask to be exempted from Android's battery optimisation restrictions, which is what keeps it from being culled by Doze and App Standby.
It is presented to the user as a Settings screen rather than a permission dialog, so like PACKAGE_USAGE_STATS it lives somewhere a quick permission review will not reach. That makes it worth reading carefully rather than dismissing: the consent model is deliberately indirect.
The manifest analysis describes it in plain terms as allowing uninterrupted background operation so the payload can actually work, and notes it takes as much battery as the device will give. It is explicitly complimentary to the other background permissions rather than useful alone.
Those companions are what give it meaning. RECEIVE_BOOT_COMPLETED restarts the implant after a reboot, the FOREGROUND_SERVICE types keep a visible worker resident, and WAKE_LOCK holds the CPU through a specific upload. Doze would quietly undo all of it by putting the device to sleep between sessions, which makes this the exemption that protects the rest of the persistence stack from Android's own housekeeping.
Related: WAKE_LOCK, RECEIVE_BOOT_COMPLETED, REQUEST_COMPANION_RUN_IN_BACKGROUND
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.