Skip to content

Instantly share code, notes, and snippets.

@rsrini7
Last active November 23, 2025 17:49
Show Gist options
  • Select an option

  • Save rsrini7/e97741466b588d539d603a1190b15f74 to your computer and use it in GitHub Desktop.

Select an option

Save rsrini7/e97741466b588d539d603a1190b15f74 to your computer and use it in GitHub Desktop.
Largest WhatsApp Data Leak in History

Largest WhatsApp Data Leak in History

Overview

  • Researchers from the University of Vienna and SBA Research uncovered a massive privacy vulnerability in WhatsApp impacting over 3.5 billion users worldwide, making it potentially the largest data leak in history.12
  • The leak exploited a flaw in WhatsApp’s contact lookup feature — a function designed to let users find others by their phone numbers.23

Vulnerability Details

  • The main vulnerability was WhatsApp's lack of effective rate limiting on the contact discovery and "Click to Chat" feature, allowing automated systems to query billions of phone numbers without being blocked.312
  • Researchers generated 63 billion phone numbers across 245 countries using a tool (based on Google's libphonenumber) and used an unofficial WhatsApp client (whatsmeow) to test for registered accounts.
  • The scraping reached incredible speeds of over 100 million phone numbers per hour from a single machine/IP, confirming 3.5 billion active WhatsApp accounts.123

Data Exposed

  • Phone numbers of all enumerated WhatsApp accounts.
  • Publicly accessible profile photos for 57% of accounts globally, with variation reaching up to 80% in some regions.
  • Public “about” or status texts were visible for 29% of accounts, often containing sensitive information such as political views, religious affiliations, sexual orientation, or links to other social media profiles.4231
  • Business account tags were visible for roughly 9% of accounts.
  • Cryptographic keys related to WhatsApp’s end-to-end encryption were also partially exposed, undermining trust in message security for some accounts.4

Security and Privacy Risks

  • The massive aggregation of this data at scale can be weaponized:
    • Creation of reverse phone books.
    • Spam, phishing, social engineering attacks.
    • Government surveillance, especially in banned countries like China, Iran, Myanmar, and North Korea.
    • Risk to government, military personnel, and activists exposing sensitive details unintentionally.
  • The exposure drew attention due to the privacy implications of default open settings, placing the burden on users to protect their information rather than privacy being embedded by default.234

Meta’s Response

  • Meta downplayed the leak, asserting the data collected was "basic publicly available information" and emphasized that private messages remained secure thanks to end-to-end encryption.314
  • The company acknowledged the flaw and said it was working on anti-scraping defenses, which were deployed after researchers publicly disclosed the vulnerability in late 2025.12
  • Meta credited the researchers under its Bug Bounty program and noted no evidence of malicious exploitation beyond the research team.41
  • The delay in significant mitigation prompted criticism, as the flaw was known since at least 2017.52

Broader Implications

  • This incident sparked global debate about responsibility for user privacy — whether companies like Meta should design platforms secure by default or if users must proactively tighten controls.23
  • Compared to privacy-focused platforms like Signal that protect user data by default, WhatsApp’s default openness contributed to this vulnerability’s scale and impact.3
  • The researchers responsibly deleted the data collected following disclosure to prevent abuse.1

Summary Table

Aspect Details
Affected Users Over 3.5 billion WhatsApp users
Method of Leak Phone number enumeration via WhatsApp’s contact lookup without rate limiting
Phone Numbers Queried 63 billion possible numbers tested
Query Speed Over 100 million checks per hour from a single machine
Publicly Exposed Data Phone numbers, profile photos (57%), about texts (29%), business tags (9%), cryptographic keys
Privacy Risks Spam, phishing, social engineering, surveillance, reverse phone books
Countries Affected Global, including banned countries like China, Iran, Myanmar, North Korea
Meta’s Position Data is publicly available; end-to-end encrypted messages were not exposed
Mitigation Anti-scraping countermeasures deployed post disclosure
Researchers University of Vienna and SBA Research
Leak Known Since At least 2017
Default Privacy Concern WhatsApp not private by default, unlike competitors like Signal

This summary captures all key points of the WhatsApp data leak incident, its mechanics, scope, implications, and responses in a detailed markdown format for clarity and reference. 6789

Footnotes

  1. https://www.theregister.com/2025/11/19/whatsapp_enumeration_flaw/ 2 3 4 5 6 7 8

  2. https://www.computing.co.uk/news/2025/security/whatsapp-leak-3-5-billion-profiles 2 3 4 5 6 7 8 9

  3. https://www.wired.com/story/a-simple-whatsapp-security-flaw-exposed-billions-phone-numbers/ 2 3 4 5 6 7 8

  4. https://cyberinsider.com/whatsapp-flaw-allowed-researchers-to-scrape-data-of-3-5-billion-users/ 2 3 4 5

  5. https://www.indiatoday.in/technology/news/story/major-whatsapp-flaw-exposed-phone-numbers-and-profile-photos-of-almost-all-phone-users-in-the-world-2822406-2025-11-19

  6. https://threema.com/en/blog/whatsapp-data-leak-2025

  7. https://techxplore.com/news/2025-11-whatsapp-vulnerability.html

  8. https://www.scworld.com/brief/record-breaking-data-leak-stems-from-whatsapp-vulnerability

  9. https://indianexpress.com/article/technology/tech-news-technology/whatsapp-india-user-profiles-photos-scraped-researchers-10374848/

Overview

In November 2025, researchers from Austria revealed what is potentially the largest data leak in history affecting WhatsApp users, with over 3.5 billion accounts exposed. This exposure was not due to a hacking attack but a vulnerability in WhatsApp’s contact lookup feature that has existed for approximately eight years. The flaw enabled researchers to automate the enumeration of 63 billion phone numbers worldwide, scraping user data at an astonishing speed of more than 100 million accounts per hour from a single machine.12

Nature of the Vulnerability

  • The core issue was WhatsApp's lack of effective rate limiting on its contact discovery mechanism, which meant automated systems could query billions of phone numbers without being blocked.
  • The vulnerability was leveraged by using an unofficial open-source WhatsApp client to brute-force the presence of phone numbers registered on the platform.
  • This flaw allowed the researchers to query the platform’s "Click to Chat" feature and contact discovery, revealing whether a number was registered and associated public profile information.3241

Data Exposed

  • Phone numbers of over 3.5 billion WhatsApp users worldwide were enumerated.
  • Approximately 57% of these accounts had publicly accessible profile photos.
  • About 29% of accounts displayed public "about" texts or status messages.
  • Additional metadata such as usernames and timestamps related to online activity could also be inferred.
  • The exposure included accounts in countries where WhatsApp is banned, such as China, Iran, Myanmar, and North Korea, raising significant risks especially for users in those jurisdictions.561

Scale and Impact

  • The researchers generated and checked 63 billion possible phone numbers, validating 3.5 billion as active WhatsApp users.
  • The data scraping was performed rapidly, at a rate of over 100 million queries per hour, indicating that a single machine/IP was sufficient to conduct massive scraping operations without intervention.21
  • India was one of the most affected countries, with 62% of Indian WhatsApp accounts leaking profile photos and related data—leading to severe privacy concerns for the country's hundreds of millions of users.7

Privacy and Security Risks

  • Although the data collected was considered "publicly available" by Meta, the aggregation and mass collection at this scale poses serious risks.
  • Such large-scale scraping enables the construction of reverse phone books, facilitating spam, phishing, impersonation, and targeted harassment.
  • People, including government or military personnel, exposed potentially sensitive personal data in their "about" fields.
  • For users in countries where WhatsApp is banned or monitored, this could facilitate government targeting and oppression.
  • The incident underscores the dangers when privacy settings are open by default rather than private by design.125

Meta’s Response and Responsibility Debate

  • Meta downplayed the severity, highlighting that the data—phone numbers, profile photos, and "about" texts—were basic publicly available information.
  • Meta stated that profile data was only visible to users who had not enabled privacy settings and that private messages remained encrypted and secure.
  • The company had been working on anti-scraping countermeasures but only deployed effective protections after the research was publicly disclosed.
  • WhatsApp's default privacy settings being open shifted privacy responsibility largely onto users rather than embedding privacy by design, unlike competitors such as Signal, which are private by default.41

Historical Context and Research Process

  • The flaw was originally identified by the researchers around 2017 but remained unpatched for several years.
  • Researchers from the University of Vienna and SBA Research performed this study responsibly, deleting the collected data after reporting the vulnerability to Meta.
  • Their findings emphasize the need for continuous independent security audits of widely used communication platforms.89103

Conclusion

This WhatsApp data leak serves as a landmark case highlighting the critical importance of "privacy by design" in platforms with billions of users. The exploit demonstrated how default open privacy settings combined with weak rate limiting can expose vast amounts of personal data, placing billions at risk of real-world harm such as spam, phishing, identity theft, and government surveillance. It has sparked debate on where privacy responsibility should lie—companies or individuals—especially in large-scale platforms where user data aggregation can magnify risks enormously.21


This detailed summary includes all key points and underscores the magnitude, technical details, impact, and responses involved in this historic WhatsApp data leak incident. 111213

Footnotes

  1. https://www.wired.com/story/a-simple-whatsapp-security-flaw-exposed-billions-phone-numbers/ 2 3 4 5 6 7

  2. https://www.theregister.com/2025/11/19/whatsapp_enumeration_flaw/ 2 3 4 5

  3. https://www.bitdefender.com/en-gb/blog/hotforsecurity/researchers-expose-whatsapp-flaw-that-let-them-scrape-data-from-3-5-billion-users-heres-why-it-matters-2 2

  4. https://www.moneycontrol.com/technology/3-5-billion-whatsapp-phone-numbers-allegedly-visible-online-through-flaw-but-meta-says-there-was-no-breach-article-13689624.html/amp 2

  5. https://www.privacyguides.org/news/2025/11/21/researchers-disclose-whatsapp-contact-discovery-vulnerability-that-identifies-3-5-billion-users/ 2

  6. https://www.indiatoday.in/technology/news/story/major-whatsapp-flaw-exposed-phone-numbers-and-profile-photos-of-almost-all-phone-users-in-the-world-2822406-2025-11-19

  7. https://www.youtube.com/watch?v=NXyBhVO222U

  8. https://www.univie.ac.at/en/news/detail/forscherinnen-entdecken-grosse-sicherheitsluecke-in-whatsapp

  9. https://socradar.io/3-5-billion-whatsapp-accounts-enumeration/

  10. https://www.techrepublic.com/article/news-whatsapp-flaw-exposed-billions-users/

  11. https://www.esecurityplanet.com/threats/whatsapp-flaw-enables-massive-scraping-of-3-5-billion-user-accounts/

  12. https://indianexpress.com/article/technology/tech-news-technology/whatsapp-india-user-profiles-photos-scraped-researchers-10374848/

  13. https://www.bankinfosecurity.com/whatsapp-api-could-bulk-leak-user-telephone-numbers-a-30099

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment