← Back to index
References / filed

BLUETOOTH_ADMIN

Manages Bluetooth state and discoverability under the legacy model, so Bluetooth can be toggled or made visible without any user consent.

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

Granted automatically at install, no prompt. BLUETOOTH_ADMIN grants administrative control over Bluetooth: enabling or disabling the radio, and changing the device's discoverability, which is what lets it appear visible to nearby devices.

The consent angle is the whole point. On modern Android versions this remains a normal permission and is granted silently, so an app can change Bluetooth state with no user awareness at all. Meanwhile Google split the underlying capability on Android 12 into BLUETOOTH_SCAN and BLUETOOTH_CONNECT, both dangerous permissions with runtime approval, and this legacy permission survives as the no-consent path to the same reach.

The manifest analysis flags exactly this asymmetry, noting that apps targeting older API levels or using legacy methods may still rely on BLUETOOTH_ADMIN and that it remains a risk of unconsented system-level changes. Making a device discoverable without consent is the more interesting half of that, since it is a step toward unwanted physical connections rather than merely a local toggle.

A fake traffic-challan app has no visible reason to need either Bluetooth permission. Like FLASHLIGHT, it reads as a template artefact rather than a capability the payload drives, and no code-level use is traced in the write-up.

Related: BLUETOOTH

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