← Back to index
References / filed

BIND_VPN_SERVICE

Holds the single per-device VPN slot, which mprivhaan uses as a blackhole tunnel that discards every packet and blocks the victim's own security VPN from starting.

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

System only as a manifest declaration. The victim grants the actual tunnel through the system VPN consent dialog once, which is exactly what the fake installer UI is engineered to obtain.

There is one VPN slot per device, and whoever holds it sees or shapes device traffic. That constraint is what makes this permission worth as much attention as it gets. A single holder means exclusivity: the operator is not adding a VPN alongside the victim's, the operator is the only VPN.

What mprivhaan builds into that slot is the opposite of what the permission implies. Its vt service constructs the tunnel and allow-lists two oracle package names so only its own traffic bypasses it. It then has a pump thread read packets off the tunnel interface in a loop and discard every byte. There is no routing and no forwarding. The write-up's phrasing is that it is a blackhole that also blocks the victim's own security VPN or a researcher's interceptor from starting.

The defensive value is easy to miss when the permission looks like a privacy feature. By occupying the slot and dropping traffic, the implant denies the victim any working VPN, including one they would install precisely because they suspect compromise. A user who tries to remediate with the obvious tool finds it silently unavailable, and the most likely explanation they will form is a broken subscription.

It is the strongest single answer to "why would this app want that", and it is a good illustration of why a permission should be read against the code behind it rather than against its documentation.