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
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers
The article from Aurorium details how WebRTC technology can leak real IP addresses even when users route traffic through proxies. It explains the peer-to-peer mechanics of WebRTC, the role of STUN servers in generating ICE candidates, and why standard TCP proxies fail to handle UDP traffic. Disabling WebRTC via flags or JavaScript extensions creates detectable anomalies that anti-fraud systems flag as non-standard environments. The recommended approach involves native emulation inside the browser kernel so that STUN requests return proxy IPs while preserving full API integrity across workers. Additional leaks through local network addresses, mDNS candidates, and IPv6 are also covered with practical verification methods using tools like BrowserLeaks and CreepJS.
Docx Anonymizer: Open-Source Chrome Extension Uses Fine-Tuned rubert-tiny2 to Anonymize Personal Data Before AI Uploads
A Russian developer has released Docx Anonymizer, a browser extension that automatically detects and replaces personal data in documents using a lightweight NER model before they reach public AI services such as ChatGPT. The tool was created to help organizations comply with Russia’s 152-FZ personal data protection law while avoiding the risks of uploading contracts and other sensitive files to cloud-based LLMs. It runs entirely locally via ONNX Runtime and WebAssembly, requires no network calls, and supports any AI chat interface. The underlying model, rubert-tiny2, was further trained through knowledge distillation on WikiANN, factRuEval, and synthetic business documents, reaching strong F1 scores for person and organization entities after int8 quantization. The extension intercepts text on the fly, performs named-entity recognition in under two seconds for typical contracts, and replaces detected entities with placeholders. The project is fully open source and designed for minimal user friction, addressing the growing problem of employees inadvertently leaking corporate and personal data to public AI platforms.
Hybrid Post-Quantum Message Sealing: X25519 + ML-KEM-1024 in Umbera Messenger with Public Rust Tests
Umbera messenger has open-sourced its cryptographic core and published seven Rust tests that anyone can run to verify its hybrid post-quantum message sealing scheme. The design combines X25519 with ML-KEM-1024 so that an attacker must break both algorithms to decrypt a message. Messages are protected by Double Ratchet for forward secrecy, sealed sender packaging, and per-message ephemeral keys derived via HKDF-SHA256 into AES-256-GCM. The relay server stores only an opaque box identifier and encrypted blob with no sender or recipient fields visible. Media calls use DTLS-SRTP end-to-end while TURN servers see only encrypted datagrams. Addresses for message boxes rotate weekly and are derived solely from the shared secret between the two parties.
Free Ad Blocker for iPhone, Android, and Desktop Uses DNS Parsing Without Libraries and Skips YouTube Influencer Ads From the First Second
A new free ad-blocking solution has been released for iPhone, Android, and desktop platforms. The tool relies on a lightweight DNS parser that operates without external libraries. It includes a dedicated mode for users who already run VPN connections. An accompanying browser extension automatically skips sponsored segments in YouTube videos, even when the advertisement begins at the zero-second mark. The developer describes the technical challenges encountered after launch and the fixes applied to maintain compatibility across operating systems. The project emphasizes user privacy by avoiding unnecessary data collection and third-party dependencies.