Russian TSPU Begins Intercepting UDP DNS Queries to Cloudflare and Google Public Resolvers
Starting approximately on the evening of August 26, Russia's TSPU system began intercepting open DNS queries directed at major public resolvers operated by Cloudflare and Google (1.1.1.1 and 8.8.8.8). Previously, only encrypted DoH endpoints from these providers were blocked.
Users immediately observed that DNS resolution for blocked domains now returns an NXDOMAIN response. The following example illustrates the behavior when querying YouTube and Rutracker:
- dig youtube.com @8.8.8.8 returns NXDOMAIN
- dig rutracker.org @1.1.1.1 returns NXDOMAIN
Tcpdump captures confirm that the NXDOMAIN reply is generated almost instantly, indicating local interception rather than a response from the actual resolver. The mechanism functions only over UDP; queries sent with the +tcp flag receive genuine A records from the original servers.
Further testing revealed that the interception relies on TTL-based routing manipulation. When a DNS query is first sent with TTL 2 (stopping just after the TSPU node) and then repeated with TTL 64, the second query often bypasses the filter and receives the real IP addresses. Sending random non-DNS packets with low TTL does not trigger the same effect.
In one notable case, a DNS query with TTL 2 elicited an ICMP TTL Exceeded message whose source IP was not 8.8.8.8 but 195.208.5.1, the address of the Russian NSDI server. This confirms that the TSPU performs destination NAT specifically on packets containing DNS queries, replacing the original resolver IP with the domestic NSDI address.
When multiple identical queries are sent in rapid succession within the same flow, the system occasionally fails and returns both NXDOMAIN and legitimate answers in quick succession. Network operators downstream of the TSPU will therefore observe a measurable drop in netflow records destined for foreign public DNS servers.
Related articles
Why Replace Proprietary BIOS and UEFI with the Fully Free GNU Boot Firmware
The Free Software Foundation announced in September 2026 that it is providing financial and legal support to the GNU Boot project, which aims to deliver a completely open-source replacement for traditional BIOS and UEFI firmware. GNU Boot builds on coreboot to initialize hardware at boot time and layers a free bootloader such as GRUB or SeaBIOS on top, ensuring no proprietary binary blobs are required. The initiative emerged after a 2022 split from Libreboot, which began accepting closed-source components to broaden hardware support, while GNU Boot strictly adheres to GNU licensing criteria that prohibit any non-free code. Supported platforms remain limited to older systems from roughly 2008–2012, including specific ThinkPad models, certain early Apple MacBooks, and a handful of AMD and Intel desktop boards, because newer Intel Boot Guard and AMD equivalent mechanisms enforce signed firmware that prevents unsigned replacements. Closed firmware from Intel Management Engine and AMD Platform Security Processor runs before the main operating system, possesses unrestricted memory access, and cannot be audited or disabled on most modern hardware. By offering reproducible builds and clearer installation instructions, GNU Boot seeks to lower the barrier for users who want to eliminate potential backdoors, Wi-Fi whitelist restrictions, and forced updates found in vendor firmware.
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.