BLUETOOTH
Legacy Bluetooth access under the pre-Android 12 model. Grants pairing and discovery without the runtime prompt the modern permissions require.
Granted automatically at install. BLUETOOTH provides access to Bluetooth functionality under Android's older Bluetooth permission model, letting an app communicate with paired devices or interact with Bluetooth capabilities exposed through the relevant APIs.
The permission is not unusual for an app that genuinely needs Bluetooth connectivity. What makes it worth noting is the model it belongs to. Google split this capability on Android 12 into BLUETOOTH_SCAN and BLUETOOTH_CONNECT, both dangerous permissions that require explicit runtime approval. The legacy permission keeps working as a way to obtain the same reach without triggering that consent flow, which is why the manifest analysis describes apps relying on it as either targeting older API levels or deliberately staying inside the older model.
Neither reading is necessarily malicious on its own, but both are the kind of detail that distinguishes a build from a template. Nothing in the write-up traces code-level use of Bluetooth, so this sits with the manifest-only entries rather than the permissions the analysis connects to named classes.
It is also the permission an app would need to enumerate nearby devices, which on the older model it could do without a prompt. That reach matters most to an implant that wants to push a payload or a lure over a local channel rather than over the network, though nothing in the write-up traces Bluetooth code either.
Related: BLUETOOTH_ADMIN
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.