Few Android permissions I have seen used often
Index of 42 Android permission notes from the mprivhaan dropper and payload: what each one grants, how Android grants it, and what malware does with it.
The mprivhaan analysis names a lot of permissions across two manifests: the dropper (com.airtel.android.provider.a3upjsn) and its decrypted payload (com.transport.gov.in). Each permission below has its own note, written in plain words, so you can read that analysis, or any future one, without stopping to look things up.
How Android hands out permissions
Four grant models cover everything below. Knowing which model a permission uses tells you how much the victim was involved.
Automatic at install. Normal permissions. The user is never asked; the app just has them. INTERNET and VIBRATE live here. Malware loves these because they cost nothing.
Runtime prompt. Dangerous permissions. Android shows a system dialog the first time the app wants access, and the user can revoke it later in Settings. Every SMS, phone, contacts, and notification permission lives here. Note that in mprivhaan, the payload treats revocation itself as a signal: its p() method reports permission changes upstream, so taking a permission away tells the operator you are onto them.
Settings toggle. Special access. No popup; the victim must be walked to a specific Settings screen and flip a switch there ("Install unknown apps", "Usage access", "Alarms and reminders"). Malware earns these with social engineering, which is exactly what the fake installer screens are for.
System only. Signature permissions. Only apps signed by the device maker or preinstalled as system apps can hold them. A sideloaded APK can declare these all day; Android will silently refuse to grant them. When you see one in a sideloaded manifest, it usually means the author reused a kit template built for a system app, or is hoping you will not check.
Network
Installing, updating, and removing apps
Staying alive in the background
FOREGROUND_SERVICEFOREGROUND_SERVICE_DATA_SYNCFOREGROUND_SERVICE_REMOTE_MESSAGINGWAKE_LOCKRECEIVE_BOOT_COMPLETEDSCHEDULE_EXACT_ALARMUSE_EXACT_ALARMREQUEST_IGNORE_BATTERY_OPTIMIZATIONSREQUEST_COMPANION_RUN_IN_BACKGROUNDREQUEST_COMPANION_USE_DATA_IN_BACKGROUNDREQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND
SMS, calls, and contacts
RECEIVE_SMSREAD_SMSSEND_SMSRECEIVE_WAP_PUSHREAD_PHONE_STATEREAD_PHONE_NUMBERSREAD_CALL_LOGCALL_PHONEREAD_CONTACTSPOST_NOTIFICATIONS
Watching and blocking other apps
The VPN slot
Accounts and sync
Bluetooth and miscellaneous hardware
How to use this page
When a future analysis names a permission, come back here first and check its grant model. Automatic-at-install permissions are free, so their presence means little and their absence can mean a lot. Runtime permissions show what the operator needed the victim to approve. Settings toggles show where the social engineering went. System-only declarations in a sideloaded app show what the kit wished for. Read that way, a manifest stops being a wall of scary names and becomes a plan of the attack, which is exactly what the mprivhaan analysis turned it into.