FLASHLIGHT
Controls the camera LED as a torch. Out of place in a fake traffic-challan app, and a useful sign of a template that requests more than it understands.
Granted automatically at install, no prompt. FLASHLIGHT lets an app switch on the camera LED as a torch, a normal permission inherited from the era when camera hardware was routinely shared.
It is genuinely puzzling in this manifest, and the write-up says so directly. A fake mParivahan traffic-challan app has no visible reason to need a torch, and the author notes doing double and triple checks to confirm the entry was real before deciding it was not a misread.
That reaction is the useful part. Compare it with VIBRATE, which the same analysis waves off as self-explanatory because haptic feedback has an obvious use in phishing screens. FLASHLIGHT has no such explanation, which makes it a marker for how the manifest was assembled rather than for what the payload does.
No code-level use is traced for it. The permissions the write-up connects to named classes and endpoints are the SMS trio, the identity pair, the call set, and the contacts list. Permissions like this one, and BLUETOOTH_ADMIN, read as entries a template added for breadth and nobody removed.
Permissions like this one are a useful calibration for reading a manifest: if a fake challan app wants a torch, the list was assembled without much filtering, and every other entry on it deserves the same scepticism as this one.
Related: VIBRATE
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.