962+ breaches tracked — check free
shield
EmailLeaked
info How it works check_circle What we check database Recent breaches help FAQ article Blog group About
search Check my email now
Privacy Terms Contact Disclaimer
arrow_back Back to all breaches
Home chevron_right Recent Breaches chevron_right Twitter (200M)
T

Twitter (200M)

MEDIUM RISK

Data breach — January 2021

In early 2023, over 200M records scraped from Twitter appeared on a popular hacking forum. The data was obtained sometime in 2021 by abusing an API that enabled email addresses to be resolved to Twitter profiles. The subsequent results were then composed into a corpus of data containing email addresses alongside public Twitter profile information including names, usernames and follower counts.

search Check if you were affected — free
211.5M
Records exposed
2021
Year of breach
4
Data types exposed
Free
To check your email

Data exposed in this breach

mailEmail addresses personNames infoSocial media profiles personUsernames

What happened in the Twitter (200M) data breach?

In early 2023, over 200M records scraped from Twitter appeared on a popular hacking forum. The data was obtained sometime in 2021 by abusing an API that enabled email addresses to be resolved to Twitter profiles. The subsequent results were then composed into a corpus of data containing email addresses alongside public Twitter profile information including names, usernames and follower counts.

The exposed data included 4 types of personal information. Learn more about what a data breach means for you.

Quick answer — was Twitter (200M) hacked?

Yes. Twitter (200M) was breached in January 2021. The breach exposed 211,524,284 records including email addresses, names, social media profiles. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.

Why was the Twitter (200M) breach so dangerous?

The Twitter (200M) breach exposed 211,524,284 records — that is 211.5M people whose personal data is now circulating on the dark web. The combination of email addresses, names, social media profiles makes this a medium-risk breach that should be addressed promptly.

Don't wait to find out — check if your email was exposed in this breach now.

What data was stolen in the Twitter (200M) breach?

warning

Email addresses — used for phishing attacks and credential stuffing against your other accounts

warning

Names — used to build profiles and target you with personalised scams

warning

Social media profiles — may be combined with other breach data to build a profile for targeted attacks

warning

Usernames — used to build profiles and target you with personalised scams

Is the Twitter (200M) breach still dangerous in 2026?

Yes. Stolen data from the Twitter (200M) breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2021 are still actively used in credential stuffing attacks today.

Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your Twitter (200M) password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.

Frequently asked about the Twitter (200M) breach

Approximately 211,524,284 user records were exposed in the Twitter (200M) breach in January 2021.

Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your Twitter (200M) password elsewhere and haven't changed it, those accounts remain at risk today.

Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full Twitter (200M) dataset and tell you instantly whether your email was exposed and what data was taken.

Change your Twitter (200M) password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.

Who was affected by the Twitter (200M) breach?

The Twitter (200M) data breach affected approximately 211,524,284 users who had accounts with the service. With 211.5M records exposed, this is one of the larger breaches tracked in our database of 970+ known breaches.

If you ever created an account with Twitter (200M) or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.

If your email was in the Twitter (200M) breach

1

Change your Twitter (200M) password immediately

Go to Twitter (200M) and change your password right now. Use a strong, unique password that you have never used anywhere else.

2

Change any account sharing that password

If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.

3

Enable two-factor authentication

Turn on 2FA on Twitter (200M) and every important account. Even if your password is known, attackers cannot get in without the second factor.

4

Check your other accounts for this breach

Run a full email check to see every breach your email appears in — not just this one.

searchCheck all my breaches — free
shield

Was your email in this breach?

Check if your email appeared in the Twitter (200M) breach and 969 other known breaches — free, instant, no signup.

search Check my email — free

No signup · Under 2 seconds · Never stored

Breach details

Breach date January 2021
Records 211,524,284
Risk level Medium
Passwords exposed No
Verified verifiedYes
View all 970+ breaches
Browse the full breach database
arrow_forward
shield

Was my email hacked?

Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.

search Check my email now — it's free

No signup required · Results in under 5 seconds · Your data is never stored

keyboard_arrow_up
keyboard_arrow_down