MyRecon OSINT
1win
On 2 November 2024, 1win was breached. 96,166,543 accounts were exposed, including dates of birth, email addresses, geographic locations. MyRecon rates it 81/100, critical. That is roughly everyone in Germany.
The password hashes in this breach were SHA-256, which sounds reassuring and is not. SHA-256 is a general-purpose hash built for speed, the same property that makes it excellent for verifying files makes it poor for storing passwords, because consumer graphics hardware can test enormous numbers of candidates per second. Proper password storage uses a deliberately slow algorithm with a per-user salt. Anyone whose password appears in a wordlist should assume it has been recovered.
The more sensitive issue is the context rather than the fields. A gambling account is inherently disclosive: its existence says something about a person that they may not have shared, and in several jurisdictions online betting is restricted or prohibited outright. Dates of birth, phone numbers, IP addresses and country data attached to that account make the holder identifiable and locatable.
That combination is what makes this data useful for extortion rather than ordinary fraud, the threat being exposure, not theft. If a message arrives demanding payment to keep an account quiet, the data behind it has been public for a long time and payment buys nothing. Report it rather than engage. And change the password everywhere it was reused, starting with any account tied to money.
The story behind the breach
In November 2024, the online betting platform 1win suffered a data breach that exposed 96M users . The exposed data included email and IP addresses, phone numbers, dates of birth, country and SHA-256 password hashes.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence. Data provided to HIBP by Leidhall.
How did it happen?
The published account does not explain the exact way the data was obtained.
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?
96,166,543 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Dates of birth, Email addresses, Geographic locations, IP addresses, Passwords, Phone numbers.
What was exposed, and why it matters
- Dates of birthOne of the three things call centres ask to verify identity, and it never changes.
- 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.
- IP addressesApproximate location at the time of use, and a way to correlate accounts across services.
- PasswordsAnyone reusing this password elsewhere has those accounts exposed too, credential stuffing is automated and tries them all within days.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
What to do if you were in it
- Change this password anywhere you reused it, starting with your email account, that is the one that can reset all the others.
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- 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 1win 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 1win breach?
dates of birth, email addresses, geographic locations, ip addresses, passwords, phone numbers. 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 2 November 2024. It was published to Have I Been Pwned on 3 February 2025, a gap of 94 days during which the data was already out.
Is the 1win 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?
96,166,543 accounts. That is roughly everyone in Germany. 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.