FOREGROUND_SERVICE
Lets background work run behind a persistent notification. The umbrella permission behind every polling worker in the mprivhaan payload.
Granted automatically at install, though the permission is only half the story: Android 9 and later require the matching runtime type, which is where the two more specific permissions in this kit come in. Declaring the umbrella alone does nothing without a foreground service type.
What it buys is survival. Android aggressively kills background work it cannot see, so an exfiltration client that wants to keep polling needs a foreground service with a visible notification. The write-up's analysis describes the payload's persistent worker holding a foreground notification slot precisely so it survives Doze and background kills while it uploads.
This is the structural permission in the kit. FOREGROUND_SERVICE_DATA_SYNC and FOREGROUND_SERVICE_REMOTE_MESSAGING declare the two types actually used, startForeground(SYNC, notification) is called with a minimal "Syncing data" notification, and POST_NOTIFICATIONS exists largely to justify that notification so the service keeps running. Without this permission the polling chain that carries SMS, contacts, and call logs upstream would be killed within minutes.
It is also why this shows up in the string pool analysis as active plumbing rather than a template leftover. The analysis notes that dataSync has no references in the malware's own classes beyond backing the service type, which is exactly what a correctly declared permission looks like.
Related: FOREGROUND_SERVICE_DATA_SYNC, WAKE_LOCK, POST_NOTIFICATIONS
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.