Yandex Deploys OPRF Protocol to Protect Phone Numbers in Mandatory Audience Measurement Data Sharing
Yandex has published a detailed technical account of how Russian audiovisual services are meeting new legal requirements to share user identifiers derived from phone numbers while avoiding a single point of compromise.
Regulatory Background
Under recent legislation, 23 registered audiovisual platforms must transmit an additional user identifier to an authorized research organization. The identifier must be consistent across services for the same normalized phone number so that the same individual can be counted once regardless of device or platform.
Why Simple Hashing Failed
An initial proposal relied on a shared secret key combined with Argon2 or HMAC-SHA256 over normalized numbers. While functionally correct, any leakage of the common key would allow an attacker to reverse all identifiers from every participating service. Yandex assessed this risk as unacceptable given the number of independent companies involved.
OPRF Construction
The chosen solution is based on Oblivious Pseudorandom Function as specified in RFC 9497. Each phone number is first normalized to E.164 format, mapped to an elliptic-curve point via hash-to-curve, and blinded with a fresh random scalar. Two independent third parties, each holding its own secret scalar, successively multiply the blinded point. After unblinding and final hashing, the service obtains a stable identifier without ever learning either secret key.
Operational Properties
- Raw phone numbers never leave the originating service or reach the research organization.
- Compromise of one third party is insufficient for offline dictionary attacks.
- Rate limits and request-volume monitoring deter malicious clients from building full lookup tables.
- Key rotation remains possible without changing identifiers already issued.
The final architecture requires each audiovisual service to interact with exactly two third-party OPRF endpoints before sending the resulting identifier to the research organization.
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.