1win Data Breach: Millions of Betting Users Exposed
1win Data Breach: Millions of Betting Users Exposed
This is an informational summary based on public reports and official sources as of November 2026; details may have changed and nothing here is a legal conclusion. Verify current status before relying on it.
The 1win data breach is one of the larger incidents reported against an online gambling platform, with user records surfacing publicly in late 2024 and later verified by the breach-notification service Have I Been Pwned (HIBP). Reported figures vary by source, so the safest summary is a range rather than a single headline number. This case study sets out what has been confirmed, where sources disagree, and what the episode teaches players about trusting a betting site with personal data.
What Happened
According to reporting by CyberInsider, news of a 1win breach first emerged on 7 November 2024 through media outlets and cybersecurity Telegram channels. A Russian-language channel said a hacker using the alias "fe0dor" had uploaded a 1win database to the exploit.in forum. That same evening, 1win's own Telegram channel, reportedly managed by its chief executive, confirmed that part of its database had been exposed. The data later circulated more widely after a user called "Smartsol" published it on the BreachForums marketplace, making it freely downloadable rather than sold.
How Many Records Were Exposed
The figures differ depending on who is counting, and that distinction matters. Per CyberInsider, initial reports on 7 November 2024 cited 450 million rows of user data, while 1win's Telegram statement put the figure at about 100 million users affected. Have I Been Pwned, which added the breach to its index, reported that the exposure covered more than 96 million users. The gap between a row count and a unique-user count has not been fully explained in public reporting, so the honest framing is that somewhere on the order of roughly 96 to 100 million users appear to be affected, with a much larger raw row count, and the exact unique figure is not definitively confirmed.
| Source | Reported figure | What it counts |
|---|---|---|
| Initial reports (per CyberInsider) | 450 million | rows of data |
| 1win official Telegram | ~100 million | users affected |
| Have I Been Pwned | 96 million-plus | users in the index |
What Data Was Involved
Based on HIBP-related reporting summarised by CyberInsider, the exposed fields included email addresses, phone numbers, IP addresses, dates of birth, geographic locations, and SHA-256 hashed passwords. Later reporting on a BreachForums leak described a 28GB user database said to include usernames, account balances, and hashed passwords, alongside a separate affiliate or partner database. The affiliate figure, described as more than 418 million records, is reported as unverified, so no firm number should be treated as settled. HIBP also noted that about 17 percent of the data was already present in its system from earlier incidents, meaning not all of it was new exposure. That overlap is a useful reminder that leaked datasets often recycle older breaches, which can inflate headline counts without representing fresh victims.
Account balances are a particularly sensitive field for a gambling platform. Where a leak reveals that an account held significant value, it can make that user a more attractive target for social-engineering attempts that pose as support or payout staff. This is why the combination of data types, rather than any one field on its own, is what makes a breach of this kind dangerous.
Extortion and the Operator's Response
CyberInsider reported that the attackers initially demanded 1 million dollars to keep the data private and later raised the demand to 15 million dollars. 1win declined to pay, and the attackers then leaked portions of the database to apply pressure. The company publicly confirmed the breach, said it had not paid any ransom, and stated that its current infrastructure is secure. Public reporting did not detail specific remediation steps, and no regulator finding against 1win over the incident has been widely reported, so the account here rests on the company's statements and the researchers' and HIBP's findings rather than any formal legal conclusion.
What It Means for Players
A breach of this scale is a reminder that the data you hand a betting site, not just your balance, is at stake. Hashed passwords are not plaintext, but weak or reused passwords can still be cracked over time, and leaked emails, phone numbers and dates of birth fuel targeted phishing. Anyone who has used 1win, or any large platform, should check their exposure on a service like Have I Been Pwned, change any reused password immediately, and switch on two-factor authentication where offered. Treat unsolicited "account security" messages after a breach as suspected phishing rather than genuine support. Genuine operators do not ask for your password or a one-time code by message, so any request of that kind is a signal to stop and verify through the official app instead.
Choosing where to play is part of the defence. Our guide on how to check if an online casino is legit covers licensing and security signals to look for, and our beginner's guide to online casinos explains the basics of how these platforms handle your account. If you are comparing operators, our roundups of the best crypto casinos and the best licensed casinos prioritise brands with verifiable licensing, and you can browse vetted options through our casino listing hub.
The 1win episode sits beside other industry data incidents we have documented, including the VIP Games data exposure, the DraftKings account-hack case, and the 108 million casino records leak. Read together, they show that large user counts and personal-data handling make gambling platforms a standing target, and that your own password hygiene is often the last line of defence.
Glossary
- Data breach: an incident in which personal data is accessed or disclosed without authorisation, whether by hacking, leak, or misconfiguration.
- Hashed password: a password stored as an irreversible mathematical fingerprint rather than plain text; strong hashing slows but does not always prevent cracking.
- Have I Been Pwned (HIBP): a free service that indexes known breaches so people can check whether their email or password appears in leaked data.
- Row count vs user count: leaked databases are measured in rows, which can exceed the number of unique people because one user may appear in many records.
- BreachForums: an online marketplace and forum where stolen data is traded or published, often after extortion attempts fail.
- Two-factor authentication (2FA): a second login step beyond a password that blocks most account takeovers even if a password leaks.
Disclaimer: This article is informational only and intended for readers aged 18 and over. It is not legal or financial advice. Figures and claims are attributed to the named public sources, are reported as ranges where sources disagree, were accurate to the best of our knowledge as of November 2026, and may change. Gamble responsibly.