← Back to index
References / filed

REQUEST_DELETE_PACKAGES

Lets an app request removal of other packages, still behind a victim confirmation, which is the uninstall half of the install chain.

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

Dangerous. REQUEST_DELETE_PACKAGES lets an app ask the system to remove other installed packages, and even with the permission the user still has to confirm, so it is a request rather than a silent capability.

In the kit it is the uninstall half of the same chain that REQUEST_INSTALL_PACKAGES opens. One puts a package on the device, the other asks to take one off, and together with UPDATE_PACKAGES_WITHOUT_USER_ACTION they describe a complete lifecycle for managing what runs on the handset.

The operational reading is worth stating plainly. An implant that can request removals can try to take out the antivirus or the security app the victim installed, and the request itself is a prompt the victim may not understand or may dismiss. It can also stage replacements, removing an old version before installing a new one to keep the gap where a visible change would be noticed.

There is no code-level use traced for it in the write-up, unlike the SMS trio or the contact and call-log workers. It sits in the manifest as declared intent, grouped with the other package-management permissions that let the kit control what is installed.

PACKAGE_USAGE_STATS is the related piece on the other side of this: it is what tells the operator which security apps are present, and therefore which ones are worth asking to remove.

Related: REQUEST_INSTALL_PACKAGES, PACKAGE_USAGE_STATS

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