REQUEST_COMPANION_RUN_IN_BACKGROUND
Lets a paired companion app keep running in the background, extending the companion device model into long-lived background work.
REQUEST_COMPANION_RUN_IN_BACKGROUND allows a companion device application to keep running in the background. The companion model is Android's framework for an app that stays associated with another, nominally a phone and its paired watch or tablet, so this extends that association into background execution.
For an implant it is a way to have background presence without declaring a foreground service, which is the mechanism the FOREGROUND_SERVICE types use. A foreground service requires a visible notification, and a notification is something a victim can see and a user can dismiss.
That makes this worth taking seriously in context. The manifest analysis describes the full companion trio as contributing to a manifest with substantial capabilities for maintaining activity outside the normal foreground application lifecycle, which is the polite version of saying it keeps the implant running quietly.
The practical catch is that the companion relationship is not something an app can just declare. It requires an actual pairing, which is why all three companion permissions in this kit sit alongside permissions that do not depend on one.
REQUEST_COMPANION_USE_DATA_IN_BACKGROUND covers network access in the background and REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND covers starting services from the background, so the trio together covers execution, networking, and services.
Related: REQUEST_COMPANION_USE_DATA_IN_BACKGROUND, REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND, FOREGROUND_SERVICE
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.