Case Study: The BetMGM Data Breach (2022)
Case Study: The BetMGM Data Breach (2022)
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 BetMGM data breach disclosed in December 2022 is one of the most widely reported security incidents in US online gambling, in part because of the scale and because of the sensitive mix of data involved. This case study summarises what BetMGM disclosed, what security researchers reported, and the safety lessons players can apply to their own accounts.
What happened
On 21 December 2022, BetMGM, the sports-betting and online casino joint venture between MGM Resorts and Entain, disclosed that an unauthorised party had obtained certain patron records. According to BetMGM's own notice, as reported by SecurityWeek and Security Affairs, the company dated the start of the incident to around May 2022 and said it learned of the breach on 28 November 2022. The exposed data varied from one customer to another.
Around the same time, a seller on a hacking forum known as BreachForums advertised a database of BetMGM customer records for sale. SecurityWeek reported the listing claimed 1,569,310 records, a figure often rounded to roughly 1.5 million in press coverage. The seller said the data covered casino customers from several US states as of November 2022. BetMGM did not confirm the attacker's figure as the definitive number of people affected.
Who and when
The affected party was BetMGM and its patrons. The key dates, as attributed to BetMGM's disclosure and reported by Security Affairs and SBC Americas, are a breach beginning around May 2022, discovery on 28 November 2022, and public disclosure on 21 December 2022. The attacker's identity and the exact method used to obtain the records were not confirmed publicly; BetMGM said only that the records were obtained in an unauthorised manner.
What the BetMGM data breach exposed
According to BetMGM's disclosure as reported by SecurityWeek and Security Affairs, the information involved varied by patron and could include the following:
| Category | Data reported as potentially involved |
|---|---|
| Identity | Names, dates of birth, hashed Social Security numbers |
| Contact | Postal address, email address, phone number |
| Account | Account identifiers such as player ID and screen name |
| Financial | Transaction information |
Importantly, BetMGM stated there was no evidence that customer passwords or account funds were accessed, and that its online operations were not compromised. In plain terms, this was a theft of stored records rather than a takeover of live accounts. The Social Security numbers were described as hashed, a form of cryptographic protection, though hashing does not make data risk-free.
The distinction between "records stolen" and "accounts taken over" matters for how worried a customer should be. In this case, the immediate danger was not someone logging in and draining a balance, because BetMGM reported no evidence of that. The longer-term danger was identity-related: a dataset combining a verified name, date of birth, address, and even a hashed Social Security number is valuable to fraudsters building a profile of a real person. That is why the response centred on credit monitoring rather than password resets alone.
Outcome and aftermath
BetMGM said it was coordinating with law enforcement and offered affected patrons two years of free credit monitoring and identity-restoration services, according to Security Affairs. The incident drew attention from state regulators in jurisdictions where BetMGM operates, and it became a frequent reference point in coverage of data security across US sportsbooks. As of writing, public reporting had not confirmed a specific regulator fine tied solely to this breach, so no penalty figure should be assumed.
The case also arrived during a wider conversation about data security in the fast-growing regulated US betting market, where operators collect unusually rich personal data to meet identity-verification and anti-money-laundering requirements. That same regulatory data, once stored, becomes a target. Security researchers noted that a breach exposing verified identity details is qualitatively different from a leak of email addresses alone, because the former cannot be undone by the customer. For players, the practical takeaway is that a breach notice from a betting operator deserves the same attention as one from a bank.
What it means for players
The BetMGM case shows that even a large, licensed, well-known operator can suffer a serious data theft, and that the risk to players often lives in stored personal data rather than in their live balance. The practical lessons are straightforward.
First, the type of data matters more than the brand's size. Dates of birth, addresses, and Social Security numbers are exactly what identity thieves want, so treat any breach notice seriously and take up free credit monitoring if it is offered. Our guide on how to check if an online casino is legit explains how to confirm you are dealing with the genuine, licensed operator in the first place.
Second, separate your gambling identity from the rest of your digital life. Use a unique email and a unique password for betting accounts, enable two-factor authentication, and never reuse a password that protects your bank or primary email. If you are new to the space, our beginner's guide to online casinos covers the basics of how accounts and verification work.
Third, choose operators that are transparent and properly licensed, and keep an eye on where your data is held. Our list of the best licensed casinos and best crypto casinos highlight operators that publish their licensing, and the full casino listing is a practical place to compare.
A licence does not guarantee that a breach will never happen, as this case shows, but a regulated operator is more likely to disclose promptly, notify affected customers, and fund remediation such as credit monitoring, which is a meaningful difference in practice.
Fourth, stay alert in the months after any breach notice, not just the first week. Stolen datasets are often traded long after an incident, so phishing attempts and identity-fraud attempts can arrive much later. Be cautious with messages that already know your name, your date of birth, or that you hold a betting account, because those personal touches are designed to lower your guard. Logging in only through the address you saved yourself, and never through a link in an email, removes most of that risk. For related incidents and the patterns they share, see our case studies on the DraftKings account hack, the Clubillion casino data leak, and the Winamax data breach.
Glossary
Hashed data: Information run through a one-way cryptographic function so it is not stored in plain text; it reduces but does not eliminate risk.
Patron records: The stored customer data a gambling operator keeps, including identity, contact, and transaction details.
BreachForums: A cybercrime forum where stolen databases are often advertised for sale.
Credit monitoring: A service that alerts you to new credit activity in your name, often offered free after a breach.
Identity restoration: Support services that help victims recover after identity theft, such as disputing fraudulent accounts.
Disclaimer: This article is informational only and is intended for readers aged 18 and over. It is not legal, financial, or security advice. Figures, dates, and allegations are attributed to the named public reports, regulators, and court records available at the time of writing and may change as matters develop. Verify the current status of any case before relying on it, protect your own accounts, and gamble responsibly.