MyRecon OSINT
Chess.com (2026)
On 3 August 2026, Chess.com (2026) was breached. 4,653,212 accounts were exposed, including email addresses, geographic locations, names. MyRecon rates it 50/100 — serious. That is about 17% of the population of Australia.
What happened
In August 2026, millions of records allegedly sourced from Chess.com were posted online. The data contained 7.3M rows with 4.6M unique email addresses, along with usernames, names, countries and data relating to users' Chess.com accounts. Analysis of the data suggested it had been obtained by scraping. When loaded into HIBP, 99% of the email addresses had already appeared in previous data breaches, further supporting the scraping theory. Read more about scrapes and data breaches.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Who was behind it
No party has been publicly confirmed as responsible, and this page will not name one. Most breaches are never formally attributed: data surfaces on a forum or inside a combined dump long after the intrusion, and the trail back to a specific actor is rarely made public. Where a group has claimed responsibility it is usually named in the account above — that claim is theirs, not a finding of ours.
What was exposed, and why it matters
- Email addressesThe address becomes a confirmed, active target — expect more phishing, better aimed.
- Geographic locationsWhere the account was used, which narrows a person down further than most people expect.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- UsernamesA handle links this account to every other place the same handle is used.
What to do if you were in it
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the Chess.com (2026) breach?
Enter it in the box at the top of this page. MyRecon checks it against this breach and every other one on record, and the address is never stored.
What data was leaked in the Chess.com (2026) breach?
email addresses, geographic locations, names, usernames. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 3 August 2026. It was published to Have I Been Pwned on 13 September 2026, a gap of 42 days during which the data was already out.
Is the Chess.com (2026) breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
4,653,212 accounts. That is about 17% of the population of Australia. That is accounts rather than people — one person often has several.
Read next
Also in the archive
Severity is scored by MyRecon from the number of accounts, the sensitivity of the specific fields exposed, and whether the breach is confirmed — not by a language model. The description above is quoted from Have I Been Pwned; the analysis around it is ours.