← Back to index
References / filed

GET_ACCOUNTS

Enumerates the accounts registered on the device, mapping which banks and services the victim uses before anything is stolen.

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

Runtime prompt, and the most useful permission in the account recon block that mprivhaan declares alongside AUTHENTICATE_ACCOUNTS, READ_SYNC_SETTINGS, READ_SYNC_STATS, and WRITE_SYNC_SETTINGS. It returns the list of accounts registered on the device: which account types are present and their identifiers.

It is more sensitive than it looks, because the account list is a service map rather than a list of credentials. Knowing which banks, mail providers, and identity services a victim has installed tells an operator which lures will be recognised as plausible and which fraud flows are worth attempting, before a single byte of actual data is taken. On Android the permission is also restricted in practice, since Android 6 separates account visibility from account access, so what returns is largely the account name and type rather than any token.

Combined with the sync permissions it rounds out the picture. READ_SYNC_SETTINGS shows how those accounts are configured, READ_SYNC_STATS shows whether they have been syncing, and WRITE_SYNC_SETTINGS allows the sync configuration to be changed. Together the five form a complete account reconnaissance set.

No active use of this permission appears in the write-up's code-level findings. It is more consistent with a template declaring a full account-related permission group, unlike the telephony permissions where the analysis traces concrete classes and endpoints. Worth noting that it is also unrelated to the campaign's actual data theft, which runs through the SMS trio and the identity pair instead.

Related: AUTHENTICATE_ACCOUNTS, READ_SYNC_SETTINGS, READ_PHONE_NUMBERS

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