Verifications.io verifications.io

Verifications.io data breach: what happened and what to do

In February 2019, an unprotected database at email validation service verifications.io exposed 763,117,241 unique email addresses, many with names, phone numbers, IP addresses and dates of birth. No passwords were included.

View all 13,115 breaches
Breach date
25 Feb 2019
Made public
9 Mar 2019
Affected
763,117,241
Data exposed
Dates of birth, Email addresses, Employers, Genders, Geographic locations, IP addresses, Job titles, Names, Phone numbers, Physical addresses
Verified
Yes
Last updated

Source: Have I Been Pwned (CC BY 4.0)

Verifications.io was a company that businesses paid to check whether email addresses on their marketing lists were valid. You probably never signed up for it. Your address got there because a company that had it sent it in for checking, which is why a breach like this surprises so many people.

What happened

In February 2019, researchers Bob Diachenko and Vinny Troia found a MongoDB database that was open to the internet with no password. According to Have I Been Pwned, it exposed 763,117,241 unique email addresses. Anyone who knew where to look could read it.

The verifications.io website went offline while the disclosure was under way. An archived copy of the site is still viewable. The database was a collection of marketing lists gathered from many sources, not a single company's customer file, so there's no one customer base to point to.

What was exposed

Every record had an email address. Many also carried extra attributes: names, phone numbers, physical addresses, IP addresses, dates of birth, genders, job titles, employers and geographic locations. No passwords were in the data.

Since the data wasn't tied to one service, it describes you as a marketing target more than as an account holder. That's useful to scammers in a different way. A name, an employer and a job title make a convincing phishing email ("Hi, I'm from your company's IT team"). A phone number and date of birth feed smishing and phone scams, and help criminals pass casual identity checks.

The company's response

There was no useful public notice to customers. The site went dark during the disclosure, and the people whose data sat in the database mostly weren't the company's customers, so most of them never heard from anyone directly.

Why this one is hard to escape

You can't ask verifications.io to delete your record, because the company is gone and the data was copied while it sat open. The same details probably also sit in other marketing databases and people-search sites, which scammers use to fill in gaps. Taking your information off the sites that can still remove it makes a leaked record less useful to anyone holding it.

What to expect now

The lists are years old, but contact data ages slowly. Email addresses and phone numbers tend to stay the same for a decade. If your address was in the file, expect a steady flow of marketing spam, and sooner or later targeted phishing that uses details like your employer.

Because this breach has no passwords, there's nothing to reset on a specific account. The risk is about what scammers can do with your contact details, so the defence is caution with messages and fewer places that hold your data.

What to do if you were in it

  1. 1

    Expect phishing that uses your details

    If a message knows your name, employer or job title, don't trust it for that reason alone. Check with the sender through a number or address you already have.

  2. 2

    Be careful with unexpected calls and texts

    Phone numbers were in many records. Don't give out codes or personal details to anyone who contacts you first, and let unknown numbers go to voicemail.

  3. 3

    Use a separate email alias for sign-ups

    An alias per service lets you see who leaks or sells your address, and you can drop one that attracts spam.

  4. 4

    Turn on two-factor authentication

    Your email address is public knowledge now, so protect the account behind it. An authenticator app or passkey beats SMS codes.

  5. 5

    Check which breaches include your email

    Run a free Serus scan to see whether your email or phone number appears in this and other breaches.

Frequently asked

Was I affected by the verifications.io breach?

Have I Been Pwned lists 763,117,241 email addresses from it. You can search yours there, or run a free Serus scan.

What was exposed in the verifications.io breach?

Email addresses in every record, and in many records also names, phone numbers, physical addresses, IP addresses, dates of birth, genders, job titles and employers. No passwords.

Why was my data on verifications.io?

The company validated email lists for other businesses. If a company that held your address used the service, your record went in, even though you never dealt with verifications.io.

Do I need to change my password?

No passwords were in the data, so there's nothing to reset because of this breach. Securing your email account with two-factor authentication is still a good idea.

Sources

Something wrong or out of date? Tell us and we'll re-check it.

Serus

Check if you're exposed in a breach with Serus

Find your leaks. Get alerted to new ones.

Run a free scan

Related guides

All guides

Related articles

All articles

Cookie preferences

Choose which categories we may use. Full details for every cookie are in our Cookie Policy.

Strictly necessary

Authentication, session management, security and fraud prevention, and saving your consent choice. Always active. The site cannot function without them.

Functional

Remember preferences such as language and settings that improve your experience.

Analytics

Help us understand how the site is used, like pages visited, interactions, and performance, so we can improve it.

Marketing & advertising

Measure our marketing and deliver more relevant ads through partners such as Google, Meta, TikTok, X, and Reddit. Used only with your consent.

Your choice is saved for 12 months and applies across serus.ai, including the app. You can change it anytime from the cookie widget or the "Cookie settings" link in the footer. Withdrawing consent does not affect processing that happened before withdrawal.