Yandex Apps Leak Pre-Trigger Audio Buffers, Payment Data, and Contacts via Reverse Engineering
Security researchers have reverse-engineered two Yandex Android applications and uncovered extensive surveillance capabilities that affect millions of users across Samsung, Xiaomi, Honor, and Realme devices. The findings, presented in a multi-part series, detail how Yandex Search and Yandex Browser collect audio, location, payment, and contact data with minimal user visibility.
Audio Pre-Trigger Buffer
The voice assistant Alice continuously records microphone input into a ring buffer. When the wake word is detected, the application sends the preceding audio segment to Yandex servers. The buffer size is not fixed in code but is controlled remotely through parameters such as HasPreroll, buffer-size-ms, and loggingSoundLengthBeforeTriggerMs. Default configuration uses 48000 samples at 16 kHz, equaling three seconds, yet the server can extend this window arbitrarily or disable the feature entirely.
Audio flows from AudioRecord through the circular buffer, Opus or AAC encoding, and WebSocket transmission to wss://uniproxy.alice.yandex.net. The pre-trigger content is also used for biometric voiceprint construction.
WiFi Fingerprinting and Passive Geolocation
Applications scan nearby WiFi access points, collecting BSSID, SSID, and RSSI values. These data are sent to startup.mobile.yandex.net for server-side geolocation accurate to 10-50 meters indoors. The same mechanism registers a passive location provider that intercepts coordinates obtained by any other application on the device and records cellular tower identifiers including MCC, MNC, Cell ID, and LAC/TAC.
Payment Data Handling
Before tokenization, primary account number (PAN) and CVV values are transmitted to mobpayment.yandex.net. Researchers contrast this server-side approach with client-side tokenization used by Stripe, Braintree, and Adyen, noting that any logging failure or compromise of intermediate servers could expose card details.
JavaScript Bridge and Contact Exfiltration
Twenty-one addJavascriptInterface calls expose 94 @JavascriptInterface methods. Any cross-site scripting vulnerability on a yandex.ru subdomain grants attackers direct access to native device functions. Contact data are monitored in real time via ContentObserver on ContactsContract.Contacts.CONTENT_URI. Names, phone numbers, emails, organizations, photos, and call logs are serialized with protobuf and uploaded over HTTP POST with OAuth authorization. The application also reads numbers from WhatsApp, Telegram, and Viber using MIME-type filters.
Additional Surveillance Mechanisms
Runtime.getRuntime().exec("logcat -d") attempts to capture system logs, which are AES-encrypted and exfiltrated. PackageManager.getInstalledApplications and shell commands enumerate all installed applications, including banking apps, VPN clients, and content blockers. Hardcoded DNS servers 77.88.8.8 and 77.88.8.1 bypass system, VPN, and DoH configurations. A native library, libquarkenstein_daemons.so, implements audio pipelines, process manipulation, and encryption routines.
Remote configuration flags exceeding seventy allow the server to enable map saving, force Alice activation, or delay permission requests for years. The analysis concludes that these practices operate within the bounds of the published terms of service yet rely on architecture considered outdated by modern payment and privacy standards.
Related articles
Personal Data in Russian Franchise Networks: Who Qualifies as Data Operator Under 152-FZ
In typical franchise models, customer personal data is collected at franchisee points, stored in the franchisor’s central system, and used for network-wide loyalty programs and marketing. The key legal question is which party determines the purposes of processing and therefore bears operator status under Federal Law No. 152-FZ. The law defines an operator as the entity that independently or jointly sets processing purposes, data composition, and actions, regardless of contractual labels. Franchisees usually act as operators when concluding contracts with customers, while franchisors become processors unless they pursue independent goals such as running loyalty schemes or sending branded advertising. When a franchisor defines its own purposes, both parties may simultaneously qualify as operators for different processing objectives, requiring separate legal bases and documentation. Proper data-processing instructions must be embedded in the commercial concession agreement and must list specific data categories, actions, security measures, and breach-notification timelines to avoid administrative fines ranging from 150,000 to 500,000 RUB.
Dynamic Sites on Yandex Cloud Storage Enable Communication Under White-List Restrictions
A developer facing mobile internet white lists explored ways to exchange encrypted messages without relying on blocked infrastructure. Initial attempts with a national messenger bot failed due to poor API documentation and account hijacking. The team then modeled the problem as three neighboring plots where Alice and Bob route messages through Eve while a slow postman handles delivery. Yandex Disk was tested as a message store accessible via direct GET and POST requests, though it required accounts and suffered from 15-25 second latency. The final approach used Yandex Cloud object storage, whose domains remained whitelisted, allowing HTML files to load and function even when only government services and select platforms were reachable.
Rawline Aggregates VK, MAX, DNS and Other Tunnels into One Multi-Platform VPN Client
Rawline is a new multi-platform client that combines various VPN protocols and non-standard transports into a single application for Android, Windows, Linux and macOS. The project is built on Throne using sing-box and Xray network cores and supports both conventional protocols and unusual transports such as VK and MAX calls, WebRTC, DNS and S3. Users can import profiles via links or QR codes, test latency, chain connections and apply per-app or per-domain routing rules. The developer paid special attention to security issues, removing unnecessary local proxy endpoints, protecting internal connections with random passwords and adding traffic ownership verification that is enabled by default on Android 10 and newer. Additional fixes were implemented after discovering that some transport bridges could be hijacked by external applications sending the first UDP packet. Source code and builds are available on GitHub.
Russia Freezes Entire Hosting Networks to Block VPN Traffic, Investigation Finds
An independent test of 435 endpoints across 154 hosting providers revealed that Russian internet providers are throttling connections to entire autonomous systems rather than individual IP addresses. Networks belonging to Hetzner, OVH, DigitalOcean, M247 and HostPapa are frozen after roughly 25 TCP packets, causing downloads to stall at around 16 KB while UDP-based WireGuard tunnels remain unaffected. The blocking is applied uniformly by multiple Russian operators including Beeline, MTS and home broadband providers, indicating a centrally distributed rule from Roskomnadzor via the TSPU filtering system. Smaller providers that rent IP space from the affected autonomous systems are also impacted, regardless of their own brand or location. Cloudflare-hosted resources currently pass the test, but the list of blocked networks has remained stable since mid-2025. The researcher published an open-source script that allows anyone to reproduce the measurements in under a minute.