Data Breaches List of X (Twitter)

Sun Jun 14

Looking for a complete X (Twitter) data breaches list? This page answers common searches like "X (Twitter) hacked," "X (Twitter) breach history," and "list of X (Twitter) data breaches" with a verified timeline, record counts, root causes, and step-by-step guidance if you may have been affected.

X (Twitter) data breach history: 200 million user rows on BreachForums, password bugs, and insider tools—Twitter/X has repeated exposure patterns. BreachHistory indexes 12 verified or attested incidents tied to X (Twitter), spanning 2010–2023. This page is a complete, searchable timeline—not a single event—linking every catalog row with context on scale, root cause, and what users should do when a new X (Twitter) notice drops.

Why X (Twitter) stays on breach trackers

Global tech brands combine massive user bases, high-value intellectual property, and complex supply chains. Attackers target X (Twitter) for credentials, source code, CRM exports, and employee directories. When you read headlines about "X (Twitter) hacked," the incident may be a consumer PII leak, a developer artifact exposure, or a third-party SaaS tenant breach—each with different remediation steps.

Data breaches list — X (Twitter)

Below are the major incidents in our catalog, newest first. Record counts use company, regulator, or Have I Been Pwned attestation where available; actor-only marketing shows as "Unverified / not disclosed."

2023 — Database of 200M+ users published on BreachForums (210M+ records)
2022 — 5.4M user records published (API vulnerability) (5.4M+ records)
2022 — Zatko whistleblower — security deficiencies (Unverified / not disclosed records)
2020 — Bitcoin scam — 130 high-profile accounts hijacked (130 records)
2018 — Passwords exposed in internal log — all users advised to change (Unverified / not disclosed records)
2018 — Twitter (X): A glitch caused some passwords to be stored in… (330M+ records)
2017 — Twitter (X): Thousands of high-profile Twitter accounts have… (Unverified / not disclosed records)
2016 — Twitter (X): Late last week, a password leak hit Twitter, and… (32M+ records)
2013 — Twitter (X): Online attackers were able to access the usernames,… (250K+ records)
2013 — 250k accounts compromised (Java vulnerability) (250K+ records)
2011 — Twitter (X): A 17-year old hacker was charged with various… (Unverified / not disclosed records)
2010 — Twitter (X): May, 330.0M records (330M+ records)

Biggest and most consequential incidents

2018 — Twitter (X): A glitch caused some passwords to be stored in…

May 2018. A glitch caused some passwords to be stored in readable text, visible on the internal computer system. Full incident record →

2010 — Twitter (X): May, 330.0M records

May. A glitch caused some passwords to be stored in readable text, visible on the internal computer system. Full incident record →

Database of 200M+ users published on BreachForums

Data on 200M+ users (emails, names, usernames) published. Scraped via API vulnerability (Jun 2021–Jan 2022). Multiple ransom attempts; Ryushi asked $200k. High-profile accounts included. Full incident record →

2016 — Twitter (X): Late last week, a password leak hit Twitter, and…

Late last week, a password leak hit Twitter, and the company locked millions of user accounts as a result. It was reported that the login credentials of more than 32 million Twitter users were compromised. According to LeakedSource, which indexes hacked credentials from data breaches, the credentials are being traded on the Dark Web for about 10 bitcoin a pop or a little under $6,000. LeakedSource goes on to note that passwords are stored as plain text files, and many seem to be attached to Full incident record →

By the numbers (catalog snapshot)

12 incidents indexed under X (Twitter) on BreachHistory
907.9M+ combined attested records across rows with disclosed numerators (many incidents overlap or count emails—not unique people)
2018 — year of the largest attested row in our catalog

Patterns in X (Twitter)'s breach history

Credential and session theft — Phishing, stuffing, and OAuth token abuse recur across tech platforms.
Cloud misconfiguration — S3 buckets, misconfigured APIs, and file shares expose data without a traditional "hack."
Extortion without precise counts — Ransomware and leak-site actors often publish before victims confirm scope.
Supply-chain spillover — npm, SDK, and CRM tenant breaches affect X (Twitter) customers even when corporate HQ databases stay intact.

What to do if you used X (Twitter)

Enable multi-factor authentication on every X (Twitter) account and linked SSO identity.
Check Have I Been Pwned when new X (Twitter) headlines appear.
Rotate passwords that were reused on email, banking, or work SSO.
Watch for phishing that cites real breach details (order numbers, usernames) to appear legitimate.
Follow official X (Twitter) security communications—not SMS links from unknown numbers.

FAQ

How many data breaches has X (Twitter) had?

BreachHistory indexes 12 verified or attested X (Twitter) data breaches spanning 2010–2023. Counts vary when researchers merge scraping, misconfiguration, and ransomware as separate events.

What is the biggest X (Twitter) data breach?

The largest attested incident in our catalog is 330M+ records (Twitter (X): A glitch caused some passwords to be stored in…). See the full timeline for sources and remediation details.

Has X (Twitter) been hacked?

Yes — X (Twitter) appears on breach trackers with 12 indexed incidents including Twitter (X): A glitch caused some passwords to be stored in…. This page links every catalog row with primary sources and what users should do if affected.

Does X (Twitter) send data breach notifications?

Regulated markets require consumer notices for many PII events. Not every source-code or scraping story triggers email alerts—read each incident row for notification status.

Explore every X (Twitter) incident on BreachHistory

Browse the full catalog: X (Twitter) breach records

Compiled from BreachHistory data/breaches.json and primary sources linked on each incident page. Updated 2026-06-15.