Russia's МВД Proposes Mandatory Purchase of Special Smartphones for Migrants to Enable Permanent Digital Location Tracking
Russia's Ministry of Internal Affairs is developing a new system of permanent digital surveillance over labor migrants that would require them to purchase a special smartphone upon entering the country.
Deputy Minister Igor Zubov told the Federation Council Committee on International Affairs that foreign nationals arriving for work or long-term stays would be obliged to buy a government-approved device. An electronic profile would be created on the smartphone, enabling police to track the owner's location continuously and block any move from one settlement to another without prior approval.
The same device would also deliver automatic notifications about expiring documents, reducing unintentional violations of migration rules.
The proposal extends an existing control framework. Since September 2025, migrants in Moscow and the Moscow region have been required to install the "Amina" application, which transmits geolocation data to the МВД. Failure to transmit location information for more than three working days results in removal from migration registration and placement on a controlled-persons list, which can lead to deportation.
By mid-December, authorities reported that more than 139,000 individuals had been deregistered through this mechanism. Starting 1 July 2026, all visa-free foreign nationals must register their entry via the RuID application and create a digital profile. A centralized state database operated by the МВД, containing information on documents, employment, housing, fines, and telephone numbers of every foreigner, has been active since 30 June.
The key distinction of Zubov's initiative is that current regulations only require installation of software on a migrant's existing phone, whereas the new plan would make purchase of a dedicated device a mandatory condition of entry itself.
Similar ideas have previously drawn criticism from human rights defenders. In 2020, activist Svetlana Gannushkina argued that obliging people to buy an expensive device is unlawful, as many migrants lack the necessary funds, technical skills, or access to such technology.
The latest proposal has been presented only as a long-term plan and has not yet been formalized in legislation; therefore, the compulsory purchase of a special smartphone is not currently required for entry into Russia.
Related articles
rkn-block-checker 0.6.0 Adds Local Web UI and Reduces False Positives on Anti-Bot Responses
The open-source tool rkn-block-checker received a major update in version 0.6.0 that improves accuracy when detecting Russian ISP censorship blocks. The previous version incorrectly flagged sites protected by anti-bot systems as blocked by Roskomnadzor because it searched for common stub-page strings without checking HTTP status codes. A new logic layer now separates rate-limit responses such as HTTP 429 from genuine provider stub pages that typically return 200 OK or 451. The release also introduces a fully local Web UI built with Python’s standard-library HTTP server and vanilla JavaScript, eliminating the need for heavy frameworks. Results stream in real time via NDJSON so users can watch checks complete without polling or WebSocket connections. The project remains available on PyPI and GitHub under the MIT license.
Digital Surveillance in Your Pocket: Audit Uncovers Tracking and Weak Cryptography in 11 Top Russian Android Apps
An independent security researcher conducted a static analysis and passive logcat review of 11 popular Russian Android applications from banks, government services, marketplaces, and navigation tools. The audit identified 237 vulnerabilities in total, including six apps signed with outdated RSA-1024 or DSA-1024 keys that violate current NIST standards. VK led the risk ranking with 11 trackers and a 98/100 surveillance score, while Gosuslugi transmitted analytics signals to VK, Yandex, Google, and Huawei ecosystems. Five apps used WebRTC ICE candidate leaks to detect VPN usage, potentially bypassing user privacy protections. Only Goskluch scored low at 42.4/100 by limiting trackers to two, avoiding VPN detection, and using a compliant RSA-2048 signing key. The methodology relied solely on MobSF, jadx, and logcat without bypassing SSL pinning or requiring root access.
Amnezia VPN Survives Coordinated Russian Censorship Campaign Targeting AmneziaWG Protocol Fingerprints
Amnezia VPN has published a detailed post-mortem on the multi-wave blocking campaign conducted by Russian authorities against its Amnezia Free and Amnezia Premium services during June and July. The company describes a shift from simple protocol blocking to sophisticated fingerprinting of AmneziaWG traffic combined with infrastructure DDoS attacks and automated IP-subnet blacklisting. Engineers closed multiple detection vectors including zero-length UDP packets, fixed-size keepalive messages, handshake timing patterns, and nonce zero bytes. The incident forced accelerated migration to AmneziaWG 2.0, discontinuation of legacy client support, and development of AmneziaWG 3.0 while expanding VLESS infrastructure as a backup. Self-hosted users largely avoided direct protocol blocks but still faced subnet-level restrictions. The report highlights how Roskomnadzor now applies cumulative scoring across multiple traffic features rather than single definitive markers.
Data Masking: 8 Critical Questions Businesses and Developers Ask About Protecting Sensitive Data
Garda expert Dmitry Larin addresses common challenges in data masking during a recent webinar titled 'Data Masking: Battle of Opinions'. The discussion covers why masking remains essential even when encryption is deployed, how to preserve application functionality after anonymization, and the performance trade-offs of processing large databases such as 5 TB PostgreSQL instances. Different masking types including static, dynamic, selective, and streaming are explained with specific use cases for DevOps pipelines, external contractors, and BI systems. The article also examines why machine learning alone is insufficient for discovering personal data and why custom scripts fail at scale across heterogeneous environments like PostgreSQL and Oracle. Practical recommendations include combining masking with encryption, using deterministic transformations for deduplication, and separating replication from masking tasks to avoid production impact.