Breach date: 2019-02-25. Added to this index: 2019-03-09. Accounts affected: about 763M. Domain: verifications.io.
What happened
In February 2019, the email address validation service verifications.io suffered a data breach. Discovered by Bob Diachenko and Vinny Troia, the breach was due to the data being stored in a MongoDB instance left publicly facing without a password and resulted in 763 million unique email addresses being exposed. Many records within the data also included additional personal attributes such as names, phone numbers, IP addresses, dates of birth and genders. No passwords were included in the data. The Verifications.io website went offline during the disclosure process, although an archived copy remains viewable.
Breach data sourced from Have I Been Pwned, used under CC BY 4.0. Additional breach metadata provided by XposedOrNot. DataExposed is an independent service and is not affiliated with or endorsed by either.
What was exposed
Dates of birth: Your full birth date, day, month and year, collected at signup for age checks, identity verification, insurance quotes, birthday offers or government services.
Email addresses: The email address you used to register or log in. It is the most common field in breaches because it doubles as your username on most sites.
Employers: The name of the company or organisation you work for, collected by professional networks, job sites, insurers, lenders and many signup forms.
Genders: The gender or sex recorded on your profile, usually picked from a list at signup, sometimes with a title such as Mr or Ms or a gender identity option beyond male and female.
Geographic locations: A general location recorded on your account, such as a country, state, city, postcode or region, either typed in by you or estimated from your IP address.
IP addresses: The network addresses your devices used when you signed up, logged in or posted, recorded by almost every website in its access logs.
Job titles: Your role or position, such as accounts payable officer, nurse or IT administrator, recorded by professional networks, business software, event registrations and marketing lists.
Names: Your first name, surname and sometimes middle name or initials, as you gave them when you signed up. It appears in almost every breach because nearly every account asks for it.
Phone numbers: Your mobile or landline number, collected at signup for contact, delivery updates, marketing and two-factor codes.
Physical addresses: Your residential, postal, billing or delivery address, stored by retailers, utilities, banks, government services and almost any company that sends you something.
What to do now
Check whether your own address is in this dataset with the free email breach check.
Review the accounts connected to this service and turn on two-factor authentication.
Turn on two-factor authentication on your email account first, because it is the reset path for everything else.
Treat calls and messages that quote real details about you as hostile until you verify them another way.
Frequently asked questions
What data was leaked in the Verifications.io breach?
The Verifications.io breach exposed Dates of birth, Email addresses, Employers, Genders, Geographic locations, IP addresses, Job titles, Names, Phone numbers, Physical addresses. About 763M accounts were affected.
Was I affected by the Verifications.io breach?
Run the free email breach check with the address you used on that service. It will tell you whether your address appears in this dataset.
What should I do about the Verifications.io breach?
Treat any message that quotes details from this breach as suspicious, turn on two-factor authentication, and consider removing your details from people-search sites if your address or phone was included.