← Back to index
References / filed

READ_PHONE_NUMBERS

Returns the SIM's own phone numbers, which the payload pairs with device identifiers for victim fingerprinting and tracks SIM swaps so a fraud victim is not lost.

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

Runtime prompt. READ_PHONE_NUMBERS returns the phone numbers attached to the SIMs on the device.

Its primary use here is the victim's own number, which completes the fingerprint tuple built by READ_PHONE_STATE. The write-up describes the android_id and phone number pair as the primary key under which everything else is filed upstream, and this is the half that is a human-readable identifier rather than an opaque device string.

The second use is the more interesting one, and it is about retention rather than collection. SimInfoRefreshWorker re-runs on a schedule, so if the victim swaps the SIM the new number is re-registered against the same victim record. Swapping the SIM is the standard response to suspected fraud, and it is the step where a naive client loses the target. This one keeps hold of them.

That is worth separating from the permissions that take data. Nothing is being exfiltrated here in the sense that contacts or SMS are. What is being maintained is the operator's ability to keep using everything already stolen, which is a quieter and more durable failure mode to guard against when triaging an incident.

GET_ACCOUNTS is in the same reconnaissance category for a different reason, since it maps services rather than identifying the handset.

Related: READ_PHONE_STATE, GET_ACCOUNTS

Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.