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
WhatsApp Help Pages Hid Secret Instructions Directing AI Bot to Avoid GDPR References
Researchers at Redact discovered hidden instructions embedded in WhatsApp's public help documentation that instructed the company's AI support chatbot to avoid recommending users contact data protection regulators. The instructions also prohibited the bot from referencing GDPR, LGPD, or CCPA when users mentioned legal proceedings or lawyers. The findings emerged after Redact analyzed 545 help pages and identified 102 concealed blocks across 80 of them. One directive explicitly told the bot not to suggest contacting supervisory authorities even when users had lost access to their phone number and could not delete their account, despite WhatsApp's own European privacy policy stating that such complaints are permitted. WhatsApp confirmed to WIRED that the blocks were intended solely for its internal chatbot and attributed their public exposure to an error. The company stated the restrictions aimed to prevent the bot from offering legal advice. All hidden blocks were removed by October 18.
WhatsApp Secretly Instructed AI Support Bot to Suppress References to Data Regulators and Privacy Laws
Investigators discovered hidden instructions embedded in WhatsApp's public help pages that directed the company's AI chatbot to avoid recommending users contact data protection authorities. The instructions also prohibited the AI from citing privacy regulations such as GDPR, LGPD, or CCPA, even when users raised these topics themselves. The directives appeared on pages about account deletion and complaints, remaining invisible to human visitors but delivered to crawlers and the AI model. WhatsApp later confirmed the text was intended for its internal support chatbot and attributed the exposure to an error that has since been corrected. The findings highlight a gap between the company's publicly stated privacy policy and the operational guidance given to its AI systems.
Developer Builds Password Manager with Plausible Deniability Using Argon2id and XChaCha20-Poly1305
A Java backend developer rewrote a personal password manager originally built with Electron and React, migrating it to Tauri and Rust while redesigning its storage to support plausible deniability. The new implementation derives keys with Argon2id using a single per-install salt and encrypts files with XChaCha20-Poly1305, storing only random 32-character hex filenames without any headers or magic bytes. Multiple decoy vaults of identical size are created automatically for every user, and all files in the folder receive synchronized timestamps to eliminate metadata-based identification of the active vault. History and sync data are stored as additional encrypted files of the same format, making it impossible to distinguish real from decoy vaults from the filesystem alone. The approach mirrors VeraCrypt hidden volumes but operates on ordinary files and folders, with the explicit goal of providing deniability when a user is compelled to reveal a password.
LxBox Evolves from VPN Client to Comprehensive Network Traffic Management Ecosystem
LxBox has grown from a personal Android client for sing-box into a full ecosystem spanning mobile, desktop, and router platforms. The project now supports a wide range of VPN and proxy protocols within a single routing framework, allowing users to manage corporate SSL VPNs, home WireGuard connections, and proxy servers together. Key security features include default ingress blocking to prevent unauthorized reverse connections through VPN tunnels and protections against traffic leaks via excluded applications. The developer introduced progressive configuration levels, from one-click WARP setup to advanced JSON editing and AI-friendly documentation. The core sing-box-lx fork ranks among the top sing-box derivatives and powers third-party tools such as the upcoming NekoBox 6. LxBox is available on Google Play, F-Droid, and GitHub, with desktop launcher support for Windows 7 and later, macOS, and Linux.