Habr•November 21, 2026•🇷🇺Translated from Russian

Why Split-Tunneling Leaks Persist in Android VPN Clients and How Work Profiles Provide a Fix

Imagine an ordinary morning: you open Claude on a paid Anthropic Max subscription, the screen flickers, the session drops, and an email arrives announcing a permanent ban. No refund is possible under Anthropic’s terms once an account is flagged for regional violation. The user never installed a shady free VPN; they run their own server through a mainstream client such as Happ or v2rayNG with the correct applications whitelisted and auto-start enabled.

Many users assume split-tunneling protects them, yet the Android network stack prevents safe coexistence of per-app routing and a genuine kill-switch. Inside the primary profile (user 0), VpnService.Builder accepts either addAllowedApplication or addDisallowedApplication lists. The only system-wide kill-switch, Lockdown mode (“Block connections without VPN”), is enforced by netd and immediately severs connectivity for every excluded application. The sole API that can carve exceptions from Lockdown, DevicePolicyManager.setAlwaysOnVpnPackage, is restricted to device or profile owners.

Consequently, two mutually exclusive choices exist: enable Lockdown and lose banking, delivery and marketplace apps, or disable it and accept fail-open behavior. Android itself terminates background VPN processes through LMKD, subscription-update restarts, Wi-Fi-to-LTE hand-offs and delayed ACTION_BOOT_COMPLETED broadcasts, each creating a window for direct traffic.

Routing the entire device through the tunnel and handling Russian domains inside Xray or sing-box introduces further problems. Mobile clients contact Cloudflare Turnstile, OAuth endpoints, Stripe, Statsig, Sentry and Datadog; any missed domain leaks the home IP. ConnectivityManager still reports TRANSPORT_VPN to excluded apps, breaking payments. Constant keep-alives also prevent proper Doze-mode battery savings.

DNS-plus-SNI-proxy solutions on a VPS encounter similar mobile-specific obstacles: QUIC traffic on UDP 443 bypasses TCP SNI proxies, applications ignore custom DNS in favor of DoH, and open proxies are quickly abused.

The only robust solution uses Android’s built-in Work Profile. Shelter combined with Xray-core in Pocket Android creates an isolated user 10. Only Claude, ChatGPT and a browser are cloned into this profile. Because Pocket Android acts as Profile Owner, it can enforce Always-on VPN plus Lockdown exclusively on user 10. All traffic (TCP, UDP, QUIC, DNS, IPv6) is either proxied or dropped; the main profile remains completely unaffected, preserving banking apps and avoiding TRANSPORT_VPN flags.

Limitations remain: the tun0 interface is still visible in /proc/net/route, GPS and SIM data are not spoofed, and a datacenter IP already blacklisted by Anthropic will still trigger bans. Nevertheless, the architecture guarantees that the real residential IP never leaks alongside proxied traffic.

Related articles

Habr•Privacy & Surveillance

Purism Announces Librem 5 v2 Smartphone on RISC-V with Hardware Kill Switches for Camera, Microphone and Connectivity

Purism has revealed the second-generation Librem 5 smartphone, marking a major shift from Arm to RISC-V architecture with the eight-core SpacemiT K1 processor. The device retains its core privacy focus through physical hardware switches that can disable the camera, microphone, GPS, Wi-Fi, Bluetooth and cellular modem. Both the Wi-Fi/Bluetooth module and the modem are designed as removable cards, allowing users to replace or completely remove them, with future plans for 5G and NFC modules. Specifications include a 5.7-inch 1440x720 display, 13 MP and 8 MP cameras, a 4500 mAh removable battery, 8 GB RAM and 128 GB storage, dual SIM support, microSD slot and headphone jack. The phone runs PureOS with the Phosh shell based on GNOME and supports desktop mode when connected to an external monitor. Purism will not add fingerprint or facial recognition due to legal concerns in the United States, pricing the device at $1,599 with developer kits expected after a crowdfunding campaign.

AntiMalware•Privacy & Surveillance

Four VLESS VPN Configurations Show Varying Lifespans Before Network Restrictions

A Habr author under the nickname PXI published results from a private experiment involving four VPN stands running the VLESS protocol. The test compared REALITY and Self-SNI TLS setups, both directly and through an intermediate server located in Russia. One REALITY configuration with an intermediate server operated for four months until manually disabled by the author. Direct REALITY connections encountered restrictions after approximately three months. The two Self-SNI TLS stands became unavailable after eight days and three days respectively. In some cases IP accessibility later recovered, suggesting possible subnet-wide blocking. The author attributes detection to metadata analysis such as packet sizes, inter-packet intervals, connection duration and traffic direction ratios rather than confirmed active probing or machine learning by DPI systems.

Habr•Privacy & Surveillance

Bye, Censor! Android App Routes Telegram and YouTube Through Local Proxy to Evade System VPN Detection

A Russian developer frustrated with music service censorship in Yandex Music and VK Music has released an open-source Android application called Bye, Censor! that provides selective proxy access instead of registering as a system-wide VPN. The tool uses the Xray core to run a password-protected SOCKS5 or HTTP proxy on localhost, allowing only configured applications such as Telegram, Firefox, and browsers to route traffic while leaving banking and other apps unaffected. The motivation stems from Android reporting VPN status to all applications, causing services to block functionality even when their own traffic does not traverse the VPN tunnel. Users must disable any system VPN, import a VLESS or VMess configuration link, and manually set proxy settings in Telegram and browser extensions such as Proxy Toggle. The application deliberately avoids system-level registration to prevent detection by apps that refuse to operate under VPN conditions. The author notes that the solution targets the most common use cases of browsing, messaging, and video streaming while accepting that other applications may remain subject to restrictions.

Habr•Privacy & Surveillance

Pocket Android: Open-Source App Uses Work Profiles to Isolate Apps Behind Dedicated Proxies

A developer has released Pocket Android, a free open-source application that leverages Android's built-in Work Profile feature to create an isolated environment for selected apps. The tool routes traffic from cloned applications exclusively through user-defined proxies while keeping banking, delivery, and government services in the main profile on direct connections. It addresses common failures of per-app exclusion lists by enforcing strict lockdown policies that prevent leaks after reboots or proxy drops. The project builds on the Shelter codebase and integrates Xray for protocol support including VLESS, REALITY, and Hysteria 2. Battery impact is minimized through event-driven status checks rather than constant timers. The approach provides practical privacy separation for services sensitive to IP changes such as Claude and ChatGPT without requiring manual proxy switching throughout the day.