RECEIVE_SMS
Delivers every incoming SMS as a live broadcast, letting the mprivhaan dropper forward sender, body and timestamp to its payload before that payload even exists.
Runtime prompt, and one of the three messaging permissions the dropper pre-approves for its payload at session commit on API 29 and above. RECEIVE_SMS is a broadcast: it hands the app each incoming message the moment it arrives, which makes it the low-latency half of the SMS theft.
The dropper uses it before the payload even exists. Its receiver, y, is a small class that reassembles PDUs so multi-part messages arrive intact, is aware of message format, and only fires when both sender and body are non-empty. When those conditions hold it triggers oracle action 70 at the payload package (oracle id 1), passing sender, message, and timestamp extras. The consequence is worth stating plainly: the dropper can read SMS from the moment it is installed, and forwards everything to wherever the payload will eventually land.
The payload runs its own receivers too, SmsReceiver and ForwardedSmsReceiver, so the data crosses the dropper and is picked up again on the far side. That is the division of labour for the whole kit visible in one permission: the dropper catches, the payload consumes.
Holding this alongside READ_SMS is what closes the gap. Broadcast interception only sees messages arriving while the implant is alive, so anything that landed during a reboot window or a force-stop is invisible to it, and the batch poller exists to catch exactly those. Between them, no OTP on the device survives.
RECEIVE_WAP_PUSH sits in the same pre-approval list and covers carrier push, which is worth reading beside this one rather than on its own.
Related: READ_SMS, SEND_SMS, RECEIVE_WAP_PUSH
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.