LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Badoo Data Breach (2013)

CRITICAL severityConfirmedHow we verify

Badoo Data Breach (2013): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·June 1, 2013

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Badoo Data Breach (2013)

Reported June 1, 2013. Approximately 112.0M people affected.

CRITICAL
Severity
112.0M
People affected
6
Data types exposed
June 1, 2013
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Badoo Data Breach (2013) (reported June 1, 2013) exposed Dates of birth, Email addresses, Genders and Names belonging to roughly 112.0M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Badoo Data Breach (2013) breach?
112.0M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

A dataset said to contain records for 112 million individuals linked to the dating platform Badoo appeared among data traders in June 2016. The material is described as having been taken several years earlier, with the incident itself dated to 2013, though the source of the data has not been confirmed by independent verification.

What happened

The records first came to wider attention in June 2016 when they began circulating among individuals who trade in stolen data. The collection is reported to include 112 million unique email addresses along with associated personal details. Available descriptions indicate the material likely originated from an earlier compromise of Badoo systems, yet the company has not issued a public confirmation of the event and the dataset has been classified as unverified.

How a breach like this happens

Incidents involving the exposure of large user databases commonly result from unauthorised access to an organisation’s servers or applications. Attackers may exploit vulnerabilities in web services, obtain credentials through other means, or copy data during a period of undetected presence within a network. Once obtained, such collections are sometimes held for years before appearing on underground markets or being offered for sale.

About Badoo

Badoo operates as an online dating and social networking service that connects users through profile information and messaging features. Services of this type routinely collect and store account details, contact information, and demographic data to facilitate matching and communication between users. A compromise at such a platform can therefore affect a broad population because the service maintains records on millions of individuals across many countries.

The information in question

The dataset is described as containing dates of birth, email addresses, genders, names, passwords stored as MD5 hashes, and usernames. These categories align with the types of information a dating platform would typically retain for user accounts. No additional categories have been confirmed, and the precise contents of every record remain unverified because the data’s authenticity has not been established through official disclosure.

Why it matters

Individuals whose information appears in such collections face the possibility that their email addresses and other details will be used for targeted phishing or account takeover attempts on other services. Passwords hashed with MD5 can, in some cases, be processed further if they are weak or reused, increasing the chance that accounts elsewhere become accessible. For the organisation, the circulation of unverified data still prompts questions about historical security practices and the handling of long-term data retention.

Were you affected?

People who held a Badoo account around 2013 can check whether their email address appears in known breach records by using a free exposure scan service that queries public breach datasets. Changing passwords on Badoo and any other sites where the same credentials may have been used remains a practical first step, along with enabling any available two-factor authentication options.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyBadoo security record
70/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Badoo’s full breach history →

More recent breaches

Astropid Data Breach (2013)December 19, 2013Torrent Invites Data Breach (2013)December 12, 2013Pixel Federation Data Breach (2013)December 4, 2013Vodafone Data Breach (2013)November 30, 2013

Latest breaches

Read GalaxyWarden’s full analysis of the Badoo Data Breach (2013) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram