← Back to index
References / filed

RECEIVE_WAP_PUSH

System-only permission for carrier push messages, which mprivhaan pre-approves for its payload as part of whitelisting the entire messaging surface at once.

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

System only, so an ordinary app cannot hold it. RECEIVE_WAP_PUSH covers carrier push messages, the binary SMS type used for MMS notifications and SIM-related updates, and it is reserved for the system role that legitimately needs it.

It appears here for one reason: it shows up in the list of permissions the dropper pre-approves for the payload at session install time, alongside SEND/RECEIVE/READ_SMS, WAP_PUSH, MMS, phone state and numbers, call log, and contacts. The write-up reads that list as the full interception set, pre-approved at session commit on API 29 and above.

That reading is the interesting part. Granting permissions a payload cannot hold is not a mistake worth much on its own, but doing it deliberately for the entire telephony messaging surface is a design signal. The author whitelisted the category wholesale rather than picking what the payload actually calls, which is consistent with the same template breadth seen in entries like FLASHLIGHT and USE_EXACT_ALARM.

For an analyst the practical takeaway is that the presence of this permission tells you about intent and about the kit's construction, not that this specific capability is exercised. The permissions the code actually uses are RECEIVE_SMS for live interception and READ_SMS for the batch sweep.