HabrSeptember 12, 2026🇷🇺Translated from Russian

Digital Surveillance in Your Pocket: Audit Uncovers Tracking and Weak Cryptography in 11 Top Russian Android Apps

An independent researcher has published a detailed audit of 11 popular Russian Android applications, revealing widespread use of tracking libraries, outdated cryptographic keys, and VPN detection mechanisms that raise significant privacy concerns.

The analysis covered major apps from banks, government services, marketplaces, and navigation providers, including VK, Sberbank, T-Bank, Gosuslugi, Avito, VTB, 2GIS, RuStore, Yandex Pay, Ozon Bank, and Goskluch. Researchers applied static analysis with MobSF, jadx, and androguard, combined with passive logcat monitoring during cold starts, without decrypting traffic or bypassing SSL pinning.

Key Findings on Cryptographic Weaknesses

Six applications still rely on legacy signing keys that fall below modern standards. VK, Sberbank, Gosuslugi, Avito, and Ozon Bank use RSA-1024, while Yandex Pay employs DSA-1024. According to NIST SP 800-57, these key sizes have been considered obsolete since 2013, creating theoretical risks for supply-chain style attacks via forged updates.

Tracker Ecosystem and Data Sharing

Huawei Mobile Services (HMS) appeared in ten of the eleven apps, with Gosuslugi containing 78,571 references alone. VK led with eleven trackers total, including heavy integration of its own VK_SDK across seven other applications in the set. Gosuslugi itself sends signals to VK, Yandex AppMetrica, Firebase, and Huawei ecosystems even before user consent.

VPN Detection via WebRTC

Five applications — VK, T-Bank, Sberbank, Gosuslugi, and Avito — scored HIGH for VPN detection through classic WebRTC ICE candidate leaks. This technique exposes real IP addresses even when users route traffic through VPN tunnels, blurring the line between anti-fraud measures and surveillance.

Standout Performer: Goskluch

Goskluch, the government electronic signature app, achieved the lowest risk score of 42.4/100. It uses a compliant RSA-2048 key, limits trackers to HMS and Firebase, shows no VPN detection, and requests only seven dangerous permissions. At first launch it contacts only RuStore, Crashlytics, and Firebase domains.

The researcher emphasized that absolute numbers are affected by code obfuscation and that the study focused on observable static patterns rather than runtime data exfiltration.

Related articles

HabrPrivacy & Surveillance

Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing

A developer has released Hydrat, a self-hosted gateway that connects devices via WireGuard while automatically managing VLESS and Tor backends to survive server blocks and quality degradation. The system maintains a pool of tested proxies, performs continuous health checks, and switches routes without requiring client-side profile changes. Two Go processes handle control logic and network enforcement separately, using SQLite for state and nftables plus Xray for traffic routing. TCP and UDP can be assigned independent exits, with geoip.dat support and custom rules to keep marketplace apps functional. The project emphasizes stability over direct connections and is designed for deployment on servers in Russian jurisdiction.

AntiMalwarePrivacy & Surveillance

OpenAI Contractors Manually Review Real User Chats in Project Lily

OpenAI has engaged hundreds of external contractors to analyze actual user conversations with ChatGPT as part of its model improvement efforts. The reviewers, working under project Lily, examine real queries that may contain personal, medical, or other sensitive information despite the use of a Privacy Filter. Contractors summarize prompts, compare four model responses, and assign ratings from one to seven while flagging behaviors such as excessive sycophancy or inappropriate emojis. User identities are hidden and some data is filtered, yet OpenAI acknowledged that not all personal information is reliably removed. The same human review process is also employed by Anthropic for its Claude model. Users can opt out of future training use through account settings, although prior data remains unaffected.

HabrPrivacy & Surveillance

UDP Proxies and QUIC Protocol: How Real IP Addresses Leak Through Anti-Detect Browsers

Anti-detect browser users relying on UDP-capable proxies face a hidden risk of real IP leakage when the browser fails to properly route UDP traffic. The QUIC protocol, which powers HTTP/3, runs over UDP and enables features like 0-RTT handshakes, independent streams, and connection migration that can bypass proxy routes. WebRTC connections using ICE, STUN, and TURN further increase exposure because they often attempt direct UDP paths outside the configured SOCKS5 proxy. Without deep network stack control such as TUN interfaces or socket interception, browsers may send WebRTC and QUIC packets through the host's real network interface. Aurorium Browser claims to solve this by natively supporting UDP proxying so that both QUIC and WebRTC traffic stays inside the tunnel. The article stresses that simply disabling WebRTC or forcing HTTP/2 fallback is insufficient and can itself create detectable anomalies for anti-fraud systems.

AntiMalwarePrivacy & Surveillance

Google to Offer Granular Controls for Advanced Protection Mode in Android 16

Google is preparing more flexible settings for its Advanced Protection security mode that first appeared in Android 16. The changes were discovered by Android Authority researchers while examining Google Play Services version 26.36.30. A new Expert features section will let users enable individual protections such as USB Protection, intrusion detection logging, and restrictions on unsafe Wi-Fi networks without activating the entire strict mode. USB Protection blocks new USB connections while the screen is locked to prevent physical attacks, though it can interfere with fast charging on Pixel 6 and newer devices. Users will also be able to opt out of automatic connections to open or risky Wi-Fi networks if they regularly use public hotspots. Intrusion Logging remains optional and stores encrypted security logs in the cloud. The update aims to preserve core security benefits while removing the all-or-nothing requirement of the current Advanced Protection implementation.