MyRecon OSINTChess.com (2026)
Behind the exposed accounts
In August 2026, millions of records allegedly sourced from Chess.com were posted online .
Follow the story
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.
How the story unfolded
Open a step to read the detail. Missing dates stay unknown.
02Entry point
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.
03Discovery and disclosure
A separate discovery or company-disclosure date is not established by this feed record.
04Added to the breach catalogue
2026-09-13. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
4,653,212 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Geographic locations, Names, Usernames.
Two details in this record deserve more weight than the total. The first is that analysis indicated the data was scraped rather than taken from a database, collected through interfaces that were working as designed, at a scale nobody intended. The second is that 99% of the addresses had already appeared in earlier breaches.
Both facts cut the same way, and not in the direction most people assume. A scrape means no password was exposed, so there is nothing to reset. A 99% overlap with previous incidents means almost nobody in this file is newly exposed. If you are in it, this is very unlikely to be the breach that matters to you, one of the earlier ones already was.
What it does add is linkage. A username joined to a real name, a country and a confirmed email address is exactly the material used to connect a pseudonymous account to a person. If your chess handle is one you also use elsewhere, that connection is now easier for anyone to make, and no password change undoes it.
The story behind the breach
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.
How did it happen?
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.
What was the motive?
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
4,653,212 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Geographic locations, Names, Usernames.
What was exposed, and why it matters
Email addresses
The address becomes a confirmed, active target, expect more phishing, better aimed.
Geographic locations
Where the account was used, which narrows a person down further than most people expect.
Names
Turns an anonymous address into an identified person, which is what makes targeted phishing possible.
Usernames
A handle links this account to every other place the same handle is used.
What to do if you were in it
Questions people ask about this breach
Was my email address in the Chess.com (2026) breach?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
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
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.