Massive Data Breach: Hacker Releases 200 Million User Records Gratis
- Hacking Intrusion: A hacker using the name ThinkingOne released more than 200 million user records linked to X, the social media platform.
- Data at Risk: The records include email addresses, names, screen names and other profile details.
- Motivations Unclear: The data was posted for free, and the hacker’s motives are unclear.
- Call for Vigilance: Security researchers urge X users to watch for phishing and secure their accounts.
- Industry Repercussions: The leak raises questions about how platforms protect user data.
What was leaked
In March 2025, a hacker using the name ThinkingOne posted a file of about 200 million user records linked to X on a hacking forum, free for anyone to download. The file contains email addresses, names, screen names, locations and other profile fields. Much of the data was already public on users’ profiles, and no passwords were included. The email addresses are the most sensitive part, because they link accounts to real people.
Davey Winder reported the leak in Forbes. The hacker said it combined data from an earlier, larger claimed leak of 2.8 billion Twitter IDs with older records, and gave no stated financial or ideological motive for releasing it.
Why give it away?
Data sets this size can sell for real money, so giving it away puzzled researchers. Some think the aim was to embarrass the platform. Others warn that a free release simply spreads the data further and faster, and that criminals will mine it for phishing.
Start your morning with the signal that matters.
Get the weekday cyber brief for the product, threat, and vendor moves that mattered after this guide was published.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Once a file like this is public, it gets copied and stored by people the victims will never know about. It cannot be taken back.
Implications for Users: Stay Alert
The leak shows how exposed personal information on large platforms can be. X account holders can act now. Turn on two-factor authentication, use a unique password, and watch for unusual account activity. Be wary of emails that claim to come from X, since attackers can use leaked addresses and screen names to make phishing messages look convincing.
Industry Response: A Call for Improved Protocols
Large platforms like X face growing scrutiny over how they protect user data. Leaks like this one keep the pressure on.
The incident may feed debate about stronger data protection rules and limits on how much user data platforms collect and expose through their APIs.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
What X users should do now
A leak of 200 million user records linked to X is a reminder that even mostly public data can be dangerous once it is compiled into one file. The full story behind the release is still unclear, but the practical risk for users is clear enough.
Account holders can tighten their own security. Platforms need to do more to stop scraping and bulk data collection before files like this end up on hacking forums.
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Citrix NetScaler CVE-2026-19490: The Auth Bypass That Went From PoC to Probes in a Day
CVE-2026-19490 is a CVSS 9.3 NetScaler Gateway/AAA auth bypass. A public PoC on Sept 2 was followed by live probes within a...
PaperCut NG/MF: The Print Server That Learned Remote Code Execution Again
CVE-2026-81578 and CVE-2026-82078 chain to pre-auth RCE on PaperCut Application Server. Confirm Emergency Patch Release 2, restrict admin exposure, and hunt like...
JFrog Artifactory CVE-2026-82329: Empty Join Key, Full Admin Token, Busy Scanners
CVE-2026-82329 lets attackers forge Artifactory admin tokens via a deterministic empty join key. Mass scanning peaked near 406,000 attempts; patch fixed builds...
Friday’s brief: Apache’s HTTP/2 fix, then Check Point break-ins, a ScreenConnect add-on and a GitHub secret stealer
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.