READ_CONTACTS
Returns the full contact list, which mprivhaan exfiltrates upstream as a lead list so one compromised phone can seed the next wave of smishing lures.
Runtime prompt, and the permission that turns a single compromise into a campaign. READ_CONTACTS returns the full contact list, and the payload exfiltrates it upstream.
What comes back is a lead list for the next wave. The lure in this campaign was a fake traffic-challan message, and once the operator holds the victim's address book the same lure can be sent to every contact on it. One compromised phone seeds dozens of smishing messages, each of which looks legitimate precisely because it came from a number the recipient actually knows.
That is how a single-kit operation scales without buying traffic, and it is the most economically valuable permission in the manifest relative to what it costs. Every other permission here enriches the operator's understanding of one victim; this one hands them the next hundred.
The exfiltration runs through the same worker architecture as the SMS and call-log paths, with a polling worker sweeping the provider and an upload worker POSTing the result, which means it also inherits the same retry behaviour when a transfer fails.
It pairs naturally with READ_CALL_LOG, since the call log adds timing and frequency on top of the names: knowing that someone calls a particular bank every Friday afternoon is worth more to a social engineer than the name alone.
Related: READ_CALL_LOG, READ_SMS
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.