ACCESS_WIFI_STATE
Reads WiFi status, SSID, BSSID and scan results under the pre-Android 12 model. Normal permission, granted at install.
Granted automatically at install. ACCESS_WIFI_STATE lets an app query WiFi status and details: the current connection state, and under the older permission model the SSID and BSSID of the joined network plus the results of WiFi scans.
The location angle is what makes it interesting rather than the WiFi part. The BSSID of the network a device is joined to is a partial location signal, and Android restricted access to it accordingly. On Android 12 and later this permission was split into BLUETOOTH_SCAN and BLUETOOTH_CONNECT, both of which are dangerous permissions requiring an explicit runtime prompt, which is why the manifest analysis flags the legacy permission as something an app targeting older API levels may still rely on.
That is the whole observation here: this is a legacy permission that keeps working as a shortcut around the newer consent model. An app declaring it is either old, or choosing not to adopt the current model, and either way it says something about the build even if the manifest gives no direct evidence of abuse.
There is no traced use of WiFi state in the write-up's code-level findings. The permissions the analysis connects to named classes and endpoints are the SMS trio, the identity pair, the call set, and the contacts list.
Related: ACCESS_NETWORK_STATE, CHANGE_WIFI_STATE
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.