Home / Data breaches / Twitter (200M)

Data breach · 2021

The Twitter (200M) data breach, explained

Twitter (200M) (twitter.com) was breached on January 1, 2021, exposing 211.5 million accounts. Here is exactly what leaked, what it means, and the order to fix things in.

211,524,284 accounts · 4 data classes · verified record

The numbers

What the record shows

211,524,284accounts in the breach
January 1, 2021date of the breach
January 5, 2023publicly indexed
~24 monthsbetween breach and public disclosure, while the data circulated and nobody knew to reset anything

What leaked

4 kinds of data were exposed

Email addresses

The universal account key. Exposed addresses get targeted with credential-stuffing and phishing that name the breached site to look legitimate.

Names

Real names turn generic spam into convincing, personally addressed phishing.

Social media profiles

Links this identity to your public profiles for correlation.

Usernames

Ties this account to your other accounts that share the handle, which is how one breach becomes a map of your online life.

In this order

What to do now

  1. Rotate the Twitter (200M) password anyway

    Passwords were not in this record, but leaked profile data makes targeted phishing against this account more convincing, and rotation costs one minute.

  2. Kill the reuse, which is the real damage

    Every account sharing that password is now one automated attempt from gone. This is the tedious part, and it is the part Repass automates: it finds the accounts and runs each site's official reset flow for you.

  3. Scan your email for the rest of your exposure

    Run the free breach scan on the address you use most. Twitter (200M) is one breach; the median active email address appears in several, and what to fix first depends on the full picture.

  4. Turn on two-factor authentication

    A leaked password with a second factor in front of it is a locked door with a stolen key that no longer fits. Prefer an authenticator app over texted codes where the service offers the choice.

Questions

Twitter (200M) breach FAQ

Was my Twitter (200M) account affected by the breach?

The record covers 211,524,284 accounts. The quick way to check is a breach scan against your own email address, which searches this breach and hundreds of others at once. Repass runs one free on its homepage.

What should I change first after the Twitter (200M) breach?

Passwords were not in this record, so the urgent risk is targeted phishing that uses the leaked details to sound legitimate. Treat unexpected Twitter (200M)-branded email with suspicion, and rotate the password anyway if it is one you reuse.

Is changing my Twitter (200M) password enough?

Only if that password lived nowhere else. Credential-stuffing takes leaked email-and-password pairs and tries them on banks, mailboxes and stores at machine speed, so the reused copies matter more than the original. A reused password is a breach of every account that shares it.

Where does this breach data come from?

From the public index maintained by Have I Been Pwned, which verifies breaches before listing them. This page renders the structured record: dates, account count and exposed data classes.

How do I find out what else has leaked about me?

Run a breach scan on your email address. It returns every verified breach that lists the address, which is the honest starting point for deciding what to reset first. Repass then resets the passwords for you, one official flow at a time, and seals each new one in an encrypted vault.

Source: the verified Twitter (200M) record at Have I Been Pwned. Checked against the index of 2026-08-20.

After the breach

Every reused password, replaced for you.

Get Started

3-day free trial · strong unique passwords · encrypted vault

Reset your passwordsRepass does it for you, free for 3 days Get Started