← Back to index
References / filed

PACKAGE_USAGE_STATS

Reads app usage history, granted through a Settings screen rather than a prompt, so the victim sees it in Usage access instead of the permission list.

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

This one is not granted through a runtime prompt. The user enables it by hand in Settings under Usage access, which means it never appears in the normal permission dialog a reviewer would check.

Once enabled it returns usage statistics about applications on the device: which apps have been used, when, and how often. The manifest analysis flags it as particularly privacy-relevant precisely because it gives visibility into the user's interaction with other applications, rather than into the device's own state.

Within the kit it belongs to the removal-resistance cluster rather than the data-theft one. Paired with BIND_ACCESSIBILITY_SERVICE it supports the tripwire that blocks Settings, package installers, and the four OEM security centres, and REORDER_TASKS is what lets the implant hold the foreground while that happens. Knowing which apps are in use is also useful reconnaissance: it tells an operator whether a security product or a competing antivirus is present.

That is a meaningfully different threat model from the SMS trio. This permission does not take anything from the victim directly; it maps the device so the implant can survive and so the operator can adapt.

Related: REORDER_TASKS, BIND_ACCESSIBILITY_SERVICE, GET_ACCOUNTS

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