CALL_PHONE
Places calls with no dialer UI, which is how the implant programs unconditional call forwarding so the attacker answers the bank's verification call.
Runtime prompt. CALL_PHONE lets an app place calls directly without going through the dialer UI, which means the call happens with no visible confirmation and the victim sees nothing unless they check the call log.
In mprivhaan it is the active half of the call attack, and what it is used for is more specific than making calls. The implant dials carrier MMI codes to switch on unconditional call forwarding to a number it fetches from its own server. The write-up traces the fetch as /getForwardingNumber/<android_id>, and the corresponding devices/call_forwarding and /ack collections in the apkleaks dump are the command and acknowledgement sides of exactly that exchange.
The consequence is a complete takeover of the victim's voice channel. From the moment forwarding is active, every incoming call rings on the attacker's phone instead. That includes the bank's verification call, the one that asks the victim to confirm a transaction. The attacker answers it, and answers as the victim, because the caller sees the victim's number.
This is the counterpart to SEND_SMS rather than a variation on it. Both permissions exist to make the infected device act on the victim's behalf in ways the victim cannot see, and both defeat a verification control rather than merely bypassing a prompt. One defeats sender-ID checks on messages, the other defeats caller recognition on calls.
READ_CALL_LOG is the reconnaissance half, supplying the social graph that tells the operator whose verification call to expect.