Hey there! You are using WhatsApp Enumerating Three Billion ... #1585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This repository contains the extended NDSS 2026 paper “Hey there! You are using WhatsApp: Enumerating Three Billion Accounts for Security and Privacy” and supporting data files, not exploit code. The work analyzes a systemic privacy weakness in WhatsApp’s contact discovery mechanism: the platform effectively exposes a remote enumeration oracle for arbitrary mobile numbers, and historically applied rate limiting/abuse controls were weak enough to allow large-scale, automated probing o...
🔧 Technical Details
Abusing phone-number contact discovery as an enumeration oracle.
Any messaging service that lets clients ask “is this phone number registered?” via an API can be abused as a presence oracle. An attacker systematically generates candidate phone numbers and feeds them into the normal contact discovery flow (e.g., by simulating address-book uploads or batched lookups). For each number, the response reveals registered vs. unregistered status. If server-side defenses are weak, this technique scales to hundreds of millions of numbers per hour, allowing attackers to build comprehensive maps from phone numbers to accounts without ever sending messages.
Optimizing enumeration using dialing-plan modeling.
Rather than brute-forcing arbitrary numeric ranges, an attacker first builds a realistic phone-number model per country using public dialing information (country codes, valid lengths, and operator allocations, as in
country-table.csv/count...🤖 Agent ActionsSummary:
country-table.*dataset (with sample generation code), explained how to correlate X25519 public-key reuse across accounts, and outlined layered defensive controls (multi-dimensional throttling, anomaly detection, PSI-based discovery, noisy responses).Tests: Not run (documentation-only change).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.