推特(X)发生28亿用户数据泄露事件——据称是内部人员所为
Twitter (X) Hit by Data Leak of 2.8B Users – Allegedly an Insider Job

原始链接: https://hackread.com/twitter-x-of-2-8-billion-data-leak-an-insider-job/

Breach Forums上的一个名为ThinkingOne的用户声称发生了28.7亿推特(X)用户的大规模数据泄露事件,这可能是历史上规模最大的社交媒体数据泄露事件。据称泄露的数据约为400GB,据说是由一位在裁员期间心怀不满的X员工泄露的,其中包含用户ID、屏幕名称、描述、位置/时区设置、关注者/推文数量以及最后一条推文的来源等个人资料元数据。值得注意的是,其中不包含电子邮件地址。 ThinkingOne将这些数据与2023年X平台较小规模的一次数据泄露事件(2.09亿用户)的数据合并,后者包含电子邮件地址,从而创建了一个包含2.01亿条记录的组合数据集。这种混合导致了混淆,错误地暗示了新的泄露事件也包含电子邮件。 28.7亿这个数字值得怀疑,因为X平台的活跃用户数量远少于此。可能的解释包括汇总/历史数据、机器人账户或从多个公共来源抓取的数据。X平台尚未承认所谓的泄露事件,也没有回应ThinkingOne试图与其联系的尝试。2025年泄露事件的来源仍然未知。

Hacker News正在讨论一起可能涉及28亿Twitter(X)用户数据的泄露事件。文章暗示泄露源于一名心怀不满的内部人士,但这尚未得到证实。许多评论者对此表示怀疑。有人指出泄露的数据(用户ID、关注者数量、位置等)似乎都是公开信息,甚至可以在archive.org上找到。另一些人强调这些数据可能并非完全来自X。文章标题的准确性也受到质疑。一位用户注意到,之前可见的发帖客户端现在已从界面中隐藏。关于泄露数据中机器人或AI账号的比例也有猜测。还有评论者预测马斯克会进行调查,同时会削弱数据保护机构的影响力。总的来说,评论语气谨慎,对报道的“泄露”事件的严重性和真实性表示质疑。

原文

A data leak involving a whopping 2.87 billion Twitter (X) users has surfaced on the infamous Breach Forums. According to a post by a user named ThinkingOne, the leak is the result of a disgruntled X employee who allegedly stole the data during a period of mass layoffs. If true, this would be the largest social media data breach in history, but surprisingly, neither X nor the broader public appears to be aware of it.

What We Know About the Breach

The original post by ThinkingOne states that the data, around 400GB worth, was likely exfiltrated during messy layoffs at X. The poster claims that they tried contacting X through multiple methods but received no response.

Frustrated with the lack of acknowledgment from X and the general public, they took matters into their own hands and decided to merge the newly leaked data with another infamous breach from January 2023.

X (Twitter) Largest Data Breach Ever? 2.8 Billion User Info Exposed
Screenshot from Breach Forums shows what ThinkingOne has posted about the alleged breach (Credit: Waqas/Hackread.com)

The 2023 Breach Recap

To understand the full scope of what was leaked, looking at the 2023 X data breach that affected around 209 million users is important. That breach exposed:

  • Display names and usernames (handles)
  • Followers count and account creation dates

At the time, X downplayed the leak, stating that it consisted of publicly available data. Despite the massive exposure of email addresses, they insisted that no sensitive or private information was involved. However, security experts warned that the combination of emails and public data could enable phishing and identity theft on a large scale.

What’s Inside the Alleged 2025 Breach?

The 2025 breach, however, is a completely different beast. Unlike the 2023 leak, it doesn’t contain email addresses, but it does hold a goldmine of profile metadata, including:

  • User IDs and screen names.
  • Profile descriptions and URLs.
  • Location and time zone settings.
  • Display names (current and from 2021).
  • Followers count from both 2021 and 2025.
  • Tweet count and timestamps of the last tweet.
  • Friends count, listed count, and favorites count.
  • Source of the last tweet (such as TweetDeck or X Web App).
  • Status settings (like whether the profile is verified or protected).

The data gives a detailed snapshot of users’ profiles and activity over time, including bios, follower counts from different years, tweet history, and even the app used for the last tweet. But the one thing it doesn’t include is the most sensitive bit: email addresses.

The Data Mashup

ThinkingOne, a well-known figure on Breach Forums for their skill in analyzing data leaks, decided to combine the 2025 leak with the 2023 one, producing a single 34GB CSV file (9GB compressed) containing 201 million merged entries. To be clear, the merged data only includes users that appeared in both breaches, creating a confusion of public and semi-public data.

This messy combination led many to believe that the 2025 leak also contained email addresses, but that’s not the case. The emails shown in the merged file are from the 2023 breach. The presence of emails in the merged dataset has given the wrong impression that the contents of the 2025 leak also include email addresses.

Why 2.8 Billion Doesn’t Add Up

As of Jan 2025, X (formerly Twitter) had around 335.7 million users, so how is it possible that data from 2.8 billion users has been leaked? One possible explanation is that the dataset includes aggregated or historical data, such as bot accounts that were created and later banned, inactive or deleted accounts that still lingered in historical records, or old data that was merged with newer data, increasing the total number of records.

Additionally, some entries might not even represent real users but could include non-user entities like API accounts, developer bots, deleted or banned profiles that remained logged somewhere, or organization and brand accounts that aren’t tied to individual users.

Another possibility is that the leaked data wasn’t exclusively obtained from Twitter itself but rather scraped from multiple public sources and merged together, including archived data from older leaks or information from third-party services linked to Twitter accounts.

Who Is ThinkingOne, and How Did They Get the Data?

One of the biggest mysteries is how ThinkingOne managed to obtain the 2025 breach data in the first place. Unlike typical hackers, they are not known for breaching systems themselves but are highly regarded for analyzing and interpreting leaked datasets. Whether they received the data from another source or conducted some sophisticated data aggregation is still unclear.

Their theory that a disgruntled employee leaked the data during the layoffs remains unconfirmed, and there’s no concrete evidence to support it; it is only a plausible hypothesis given the timing and internal mess at X.

Why the Silence from X?

If the claims are true, this is not just a massive breach in size but also a blow to user privacy. Additionally, whether this was an inside job or not, users are left with more questions than answers: How much of their data has been “taken”? Who’s behind the leak? And why hasn’t X said anything about it, even after ThinkingOne tried reaching out multiple times?

联系我们 contact @ memedata.com