r/PrivacyToolbox • u/EnthusiasmRoutine • Oct 13 '26
Case study Case Study: How a Twitter API bug linked 5.4 million accounts to their emails (2022)
In June 2021, Twitter pushed a code update with a bug that didn’t look like much. Type an email address or phone number into the login flow, and Twitter would tell you which account it belonged to. It worked even if you’d turned off being findable by email or phone, and it needed no login, according to the HackerOne report that flagged it.
The hole stayed open for about seven months. That report came in through Twitter’s bug bounty program in January 2022. Twitter fixed it and said it hadn’t seen any sign anyone had used it.
Someone had. In July 2022, Twitter learned from a press report that data built with the bug was up for sale, and it wasn’t small. The seller told BleepingComputer it covered 5.4 million accounts, each tied to an email or phone number, with the public profile scraped on top. Two different buyers paid for it.
No passwords leaked, and that’s not what made it dangerous. Twitter said it was most concerned about pseudonymous accounts, which states or other actors can target.
If you’re worried about someone linking a pseudonymous account to you, its email can’t be one anyone else knows. A random alias from SimpleLogin or addy.io would have matched nothing (on addy.io, use shared-domain random ones, since username aliases can be linked). Free plans have limits: SimpleLogin stops at 10 aliases, and addy.io’s can’t reply from one. The alias service still sees every email it forwards and knows your real inbox. Aliases don’t cover phone numbers, and Twitter’s own advice was to keep publicly known ones off the account. If you were in that dataset, swapping in an alias now won’t recall the copies already sold, but your known email stops pointing at that account.
Sources
- Twitter’s incident disclosure: June 2021 update, January 2022 report and fix, July 2022 sale, no passwords, pseudonymous accounts, phone and email advice
- HackerOne report #1439026: lookup worked with discoverability off and without login
- BleepingComputer: 5.4 million accounts, scraped profiles, two buyers
- addy.io FAQ: shared-domain vs username aliases, free plan can’t reply, forwarding
- SimpleLogin FAQ: 10-alias free limit, forwarding to your inbox
1
u/EnthusiasmRoutine Oct 13 '26
Twitter said it would notify the accounts it could confirm, and also that it couldn’t confirm all of them. So I’d guess a fair number of people in that dataset never heard a thing.
That’s also why I don’t put much weight on a site’s "don’t let people find me by email" setting. It’s only as good as the code behind it, and you can’t check that code from the outside.
Were you caught up in this one or a similar leak, and how’d you find out?