REQUEST_INSTALL_PACKAGES
Lets an app install other APKs once the victim enables Install unknown apps, which is the hinge the whole two-package dropper turns on.
Dangerous, and the manifest analysis marks the jump to it as a clear escalation from the run of minor permissions before it. REQUEST_INSTALL_PACKAGES lets an app request installation of APKs on the device, which requires the user to enable Install unknown apps for that app first.
It still needs user interaction, so it would not be alarming alone. What makes it matter here is that this is the hinge the entire two-package architecture turns on: the dropper's whole job is to get a second, unlabelled payload onto the device, and this permission is the only way that happens.
The string pool shows the chain working. Alongside this permission the analysis lists canRequestPackageInstalls, getPackageInstaller, setInstallLocation, and the application/vnd.android.package-archive MIME type, which together are the full install path rather than a single call. The victim is walked through enabling the setting, then the payload is fetched and installed.
INSTALL_SHORTCUT completes the sequence on the other side, keeping the fake icon present after the installer finishes, so the lure the victim originally tapped is still there afterwards.
The pair with UPDATE_PACKAGES_WITHOUT_USER_ACTION is what makes the manifest genuinely alarming, since together they would allow a fully silent install-and-replace chain with no consent step at all.
Related: UPDATE_PACKAGES_WITHOUT_USER_ACTION, REQUEST_DELETE_PACKAGES, INSTALL_SHORTCUT
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.