Case Study: The 108 Million Casino Records Leak (2019)

Published:
Updated:
Case study of the 2019 casino data breach that exposed 108 million betting records

Case Study: The 108 Million Casino Records Leak (2019)

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 casino data breach 2019 known as the 108 million records leak is one of the clearest lessons online gamblers have about how a single misconfigured server can expose years of personal betting history. No hacker had to break anything. A database was simply left open to the internet without a password, and anyone who knew where to look could read it. This case study summarises what was found, who found it, and the practical red flags players can take from it.

What happened

In January 2019, security researcher Justin Paine discovered an Elasticsearch server that was exposed online with no authentication, meaning no password was required to view its contents. According to reporting by ZDNet, which first covered the find, and by Security Affairs, the server held records relating to roughly 108 million bets placed through a group of online casino and betting websites. Infosecurity Magazine reported that researchers found more than one unprotected Elasticsearch instance connected to the same operation.

Because the data was aggregated across several web domains, analysts suggested it was collected either through an affiliate arrangement or by a single company running multiple betting portals. The common thread, according to Security Affairs, was that the brands appeared to share either the same building in Limassol, Cyprus, or the same eGaming licence issued under Curacao.

Who and when

The discovery was attributed to Justin Paine and publicised in late January 2019. Security Affairs, written by Pierluigi Paganini, named four casino domains linked to the exposed data: kahunacasino.com, azur-casino.com, easybet.com, and viproomcasino.net. Reports noted the server was hosted with the provider OVH and was later taken offline, though the researcher said he could not confirm whether the operator or the host had closed access. No regulator publicly announced a fine in connection with the incident at the time, and the exact corporate ownership behind the linked brands was not fully confirmed in public reporting.

What the casino data breach 2019 exposed

According to Security Affairs and other security outlets covering the find, the exposed records included a wide mix of personal and account data:

CategoryExamples reported
IdentityReal names, home addresses, dates of birth, phone numbers, email addresses
AccountSite usernames, account balances, last login details
ActivityLists of games played, deposits and withdrawals, individual bets
TechnicalIP addresses, browser and operating-system details

Reports indicated that some payment-card information appeared in the data, but the researcher said it did not contain full financial details such as complete card numbers. Because this point was qualified in the original coverage, players should treat the payment exposure as partial rather than assuming full card data was published. The precise number of individual people affected, as opposed to the 108 million bets logged, was not confirmed publicly.

Why an open database is so dangerous

An exposure like this is more serious than it first sounds, because the attacker does no work and leaves few traces. With an unsecured Elasticsearch server, there is no password to guess and no malware to deploy; a search engine for exposed devices is often enough to find the data. That also means it is difficult to know how many people copied the records before the server was taken offline. The researcher who found it, Justin Paine, could confirm the exposure but not who else had accessed it, which is a common and troubling feature of these cases.

For the people in the database, the risk is long-lived. Unlike a stolen password, which you can change in a minute, your name, date of birth, home address, and betting history cannot be reset. If that information circulates, it can be reused for years in phishing emails, fake "account verification" messages, and targeted scams that reference real betting activity to appear convincing. A message that correctly names a game you played or a recent withdrawal is far more persuasive than a generic one, and that is exactly the kind of detail this leak contained.

What it means for players

The incident is a textbook example of an exposure caused by weak internal security rather than a sophisticated attack. For a player, the brand name on the website tells you little about how carefully that operator stores your data behind the scenes. The red flags and habits worth taking away are practical ones.

First, treat every deposit as a disclosure of sensitive data. Once you register, your name, address, date of birth, and betting history sit in someone's database, and your control over that data ends at the point you hand it over. Choosing operators that publish a clear licence and privacy policy matters, which is why our guide to choosing a safe online casino stresses verifying the operating company before you register.

Second, assume breaches happen and reduce what a single leak can do. Use a unique password for every gambling account, enable two-factor authentication where offered, and keep deposits modest with reputable payment methods. If you compare mobile options from our roundup of the best casino apps, apply the same scrutiny to data handling that you would to bonuses.

Third, watch for brands that share hidden infrastructure. A cluster of casinos operating from one address or one licence can share one point of failure, as this case suggested. Our casino blacklist and verification guide explains how to research ownership and complaint patterns before trusting a site, and the full casino listing is a starting point for licensed options. If you are chasing promotions, our overview of this month's new casino bonuses is best read alongside a security check, not instead of one.

Finally, be alert to scams that follow a leak. If your details were in a dataset like this, you may receive emails or calls that reference your real betting activity to seem legitimate. Treat any unexpected "verify your account" or "claim your winnings" message with suspicion, never click links in it, and log in only through the address you already know. For comparison with other incidents, see our related case studies on the Winamax data breach, the BetMGM data breach, and a separate operator breach case. Each shows a different failure mode, from open databases to stolen customer records, and together they explain why data security deserves as much weight as odds or bonuses when you choose where to play.

Glossary

Elasticsearch: A popular search-and-analytics database engine; left unsecured, it can expose all stored records to anyone online.

Misconfiguration: A setup error, such as removing a password requirement, that exposes data without any hacking.

White-label / affiliate group: An arrangement where several branded casinos share one underlying operator, platform, or licence.

Data aggregation: Combining records from multiple sites or sources into one dataset, which concentrates risk if that store is breached.

Personally identifiable information (PII): Data such as name, address, and date of birth that can identify a specific individual.

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.

Leave a Comment
TOP PRESS RELEASE