READ_PHONE_STATE
Exposes device identifiers and SIM info, which the mprivhaan payload uses as the primary key for victim fingerprinting and re-registration after a SIM change.
Runtime prompt, and the anchor of the whole victim record. READ_PHONE_STATE exposes device identifiers, call state, the SIM serial, and operator information.
It feeds DeviceInfoHelper, and the write-up is clear about what that produces: a victim fingerprint. The android_id paired with the phone number becomes the primary key under which everything else is filed upstream, which is why the forwarding-number lookup is keyed as /getForwardingNumber/<android_id>. Without a stable identifier the operator has a pile of stolen data with no owner; with it, every SMS batch and contact list has an owner and a session.
READ_PHONE_NUMBERS supplies the other half of that tuple. Together the pair is described in the write-up as serving two purposes, the second of which is SimInfoRefreshWorker: re-running on a schedule to detect a SIM swap. Swapping the SIM is the classic victim response to suspected fraud, and a client that lost the record on every swap would lose the victim at exactly the moment they are most likely to be cooperative.
So this permission is not theft on its own. It is the bookkeeping that makes the theft addressable and durable.
Related: READ_PHONE_NUMBERS, READ_CALL_LOG
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.