Amnezia VPN Survives Coordinated Russian Censorship Campaign Targeting AmneziaWG Protocol Fingerprints
Amnezia VPN has released a comprehensive account of the intense blocking campaign Russian authorities waged against its services this summer, detailing how the company restored stable operation of Amnezia Free and Amnezia Premium after repeated waves of sophisticated censorship.
Attack Overview
The campaign was not a conventional protocol block but a coordinated infrastructure attack. Operators observed targeted reconnaissance of the API, service behavior, and infrastructure logic, accompanied by DDoS attempts and direct attacks on the API. While the API itself resisted compromise thanks to prior audits, individual components were successfully flooded. The company also faced DDoS against its website; because it uses Amazon CloudFront, the 100k–500k RPS peaks were mitigated through rapid rate-limit activation by Amazon.
Roskomnadzor changed its blocking strategy. Instead of blocking protocols outright, censors now fingerprint traffic patterns, map servers receiving matching traffic, and automatically blacklist addresses and entire subnets. Blocks are rolled out sequentially rather than simultaneously, allowing the service to recover from one wave before the next set of rules is deployed.
Technical Mitigations Implemented
Amnezia closed several protocol fingerprints: zero-length UDP packets in certain clients, fixed-size keepalive packets, handshake timing artifacts, nonce zero bytes, and related infrastructure detection vectors. After multiple client updates, mass blocking of newly deployed servers largely ceased. Connections from outdated Amnezia Premium clients are now disabled. Self-hosted AmneziaWG installations were mostly unaffected by protocol-level rules, though some users still encountered subnet blocks.
Timeline of the Incident
The first wave began on the night of 20 May with numerous servers blocked alongside DDoS and apparent replay or scanning activity against AmneziaWG. Subsequent waves on 1 June, 7 July, 10 July, and 25 July combined IP blacklisting, subnet monitoring, API scanning, phishing attempts against staff, and automated detection of fresh servers within hours of deployment. The active phase lasted roughly six weeks.
Engineers discovered that AmneziaWG 1.0 and 1.5 versions were identifiable by fixed packet sequences following a predictable initial handshake. This prompted an accelerated rollout of AmneziaWG 2.0, which dropped support for Windows 7, Android 8, and certain router configurations. Additional fixes addressed keepalive packets and zero-length UDP packets on specific platforms.
Future Defenses and Infrastructure Changes
Work on AmneziaWG 3.0 is underway to eliminate remaining structural features such as packet-size sequences, inter-packet timing, post-handshake behavior, and repeatable combinations that allow cumulative scoring. The company is also doubling server capacity for its VLESS infrastructure to provide resilient fallback connectivity that survives both protocol and IP-based blocking.
Related articles
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.
MAX Desktop Client Tested for VPN Detection on Windows, No Tracking Signs Found
A Habra user named Slava_B conducted an experiment on September 8, 2026, to determine whether the MAX desktop client on Windows could detect or route traffic through a VPN configured at the router level. The setup used a Keenetic router that directed Russian resources directly while sending other connections via an OpenConnect tunnel to a European VPS, with no VPN client or virtual adapter present in Windows itself. Monitoring tools including Process Monitor, Wireshark, TCPView, and tcpdump revealed that MAX.exe and MAX-service.exe processes communicate locally and connect to MAX/ONEME infrastructure along with AppTracer services. The application repeatedly accessed MachineGuid, computer name, proxy settings, device IDs, and microphone/camera information, though these reads may support diagnostics and anti-fraud functions. No connections appeared on the VPN interface, and the client did not attempt to reach IP-checking services, Telegram, or WhatsApp. The researcher noted that TLS traffic was not decrypted, so actual transmission of identifiers could not be confirmed, and results apply only to this router-based configuration.
PII-Guard: Open-Source Detector for Personal Data in Russian Text
Andrey Ivanov, an NLP researcher at red_mad_robot, has released PII-Guard, an open-source system that detects and masks personal data in Russian text before it reaches language models. The tool combines rule-based checks with a fine-tuned ruBert-base NER model to handle names, addresses, phones, passports, INN, SNILS, bank cards and other entities. It replaces detected PII with structured XML-like tags that preserve grammatical information such as gender and entity ID, allowing models to generate coherent responses that are later restored with real values. The hybrid pipeline first applies normalization, pattern matching, Luhn and weighted checksum validation, and context windows with positive and negative keywords, then merges results with model predictions via an arbitration module. Evaluation on four public datasets, including Hivetrace, alexen2 and alrosait, shows PII-Guard outperforming other open solutions on both strict span matching and type-overlap micro-F1 metrics. The project, including datasets and code, is available on GitHub and aims to reduce leakage risks while maintaining downstream model utility.
Google to Add Explicit Content Warnings in Android System Photo Picker
Google is preparing a new safety feature for the system photo picker in Android that will scan images and videos for explicit or nude content. The tool is designed to warn users before they share intimate photographs, whether accidentally or due to a momentary lapse in judgment. This functionality will operate at the system level, meaning it applies across multiple apps that use the built-in photo selector. The feature aims to reduce the risk of unintended distribution of private images that could lead to embarrassment or privacy violations. By integrating the check directly into Android, Google seeks to provide a consistent layer of protection without requiring third-party applications to implement similar logic themselves.