Clubillion Casino Data Leak: Millions of Players Exposed

Published:
Updated:
Clubillion casino data leak case study showing exposed player records from an unsecured database

Clubillion Casino Data Leak: Millions of Players 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 clubillion data leak exposed the personal and activity records of players of a popular free casino game in 2020, after researchers found an unsecured database open to anyone who knew where to look. According to the cybersecurity research team at vpnMentor, the leak involved an enormous, continuously updated store of player logs rather than a one-off dump. This case study sets out who found it, what was exposed, and why a "free" social casino can still put your data at serious risk.

What Happened

Clubillion is a free online casino game for iOS and Android offering dozens of slot titles. According to vpnMentor, its research team, led by Noam Rotem and Ran Locar, discovered the breach on 19 March 2020 during a large-scale web-mapping project. The exposed database was an unsecured, unencrypted Elasticsearch instance hosted on Amazon Web Services (AWS) with no password protection, meaning the records were reachable without any hacking at all. This was a misconfiguration leak, not a reported intrusion, which is an important distinction: the data was left open rather than stolen through an attack.

How Big Was the Leak

The scale was in the throughput rather than a single total. Per vpnMentor, the database was logging about 200 million new records per day, and sometimes considerably more, adding over 50GB of records daily. The researchers did not publish a total count of unique users. Instead they listed average daily active users for sample countries, including more than 10,000 in the United States, 7,792 in Canada, 6,251 in Australia, 3,859 in Brazil, and 2,407 in Italy, and noted that many other countries were affected. Because no single verified total user figure was published, this case is best described by its daily volume, not by a headline "number of victims" that cannot be confirmed.

What Data Was Exposed

According to vpnMentor, the records were technical logs of player actions, such as entering a game, wins, losses, and account creation or updates. Within those logs the exposed personal information included IP addresses, email addresses, winnings, and private messages, and the researchers noted transaction errors from attempted card payments. Reporting by Infosecurity Magazine and the security vendor Bitdefender echoed that the exposure centred on personally identifiable information for a very large active user base. The combination of email address, location data and in-app activity is enough to support convincing phishing, which is the chief risk the researchers highlighted. Private messages are especially sensitive, because the words people write inside an app are not something they expect a stranger to read, and they can reveal personal details that a scammer can reuse.

It is worth being precise about what was not reported. There is no public indication that full payment-card numbers were stored in plain text, only that transaction errors from attempted card payments appeared in the logs. Stating more than the sources support would overstate the harm, so the accurate reading is that the exposure centred on identity and activity data rather than directly usable financial credentials.

Who Operated It and the Response

vpnMentor reported that the iOS version of Clubillion was listed under the developer Ouroboros and the Android version under T7 Games, and said both were most likely owned by the same company, though it did not confirm the corporate ownership definitively. The disclosure timeline, per vpnMentor, ran as follows: the breach was discovered on 19 March 2020, the app's developers were contacted on 23 March, AWS was contacted with details on 31 March, and the database was closed on or around 5 April 2020. vpnMentor said it did not receive a response from the developers before publication, and no regulator finding or enforcement action over the incident has been widely reported, so the account here rests on the researchers' findings rather than any legal conclusion.

What It Means for Players

The lesson is that "free to play" does not mean "safe with your data." A social casino that never touches your bankroll can still hold your email, IP address, approximate location and message history, and an open database exposes all of it. Anyone who played Clubillion in that period should assume their email may be in the wild, stay alert to gambling-themed phishing, and change any password reused from that account elsewhere. Checking exposure on a breach-notification service and enabling two-factor authentication on linked email accounts are sensible follow-ups. If the same email was used to sign up elsewhere, assume it may now receive more spam and targeted lures, and be slower to trust messages that arrive out of the blue.

There is also a design lesson for anyone evaluating apps. The Clubillion leak did not require a sophisticated attacker; an open, password-free database did the damage on its own. An operator that leaves such a system exposed is telling you something about its security culture, and that culture is as relevant to your decision as the games or the bonuses on offer.

Before installing any casino app, it is worth weighing how the operator handles data and licensing. Our guide to choosing a safe online casino covers the checks that separate accountable brands from ones that leave data exposed, and the casino blacklist and verification guide explains how to confirm a brand's track record. If you are comparing mobile options, our roundup of the best casino apps for 2026 favours operators with clear licensing and security practices, the latest casino bonuses guide helps you read offers calmly, and you can browse vetted brands through our casino listing hub.

Clubillion belongs to a wider pattern of gambling-sector data incidents, alongside the Caesars ransom-payment case, the BetMGM data breach, and a broader operator breach case we have documented. The recurring message is that a casino's security posture is part of its trustworthiness, and an open database is as damaging as a hostile hack.

Glossary

  • Data leak: exposure of data through a misconfiguration or open system, as opposed to a breach caused by an active intrusion.
  • Elasticsearch: a popular database and search engine that, if left without a password, can expose all its stored records to the public internet.
  • Social casino: a free-to-play casino-style app that offers no real-money payouts but still collects personal data and in-app activity.
  • Personally identifiable information (PII): data such as email address, IP address, or location that can identify a specific person.
  • Responsible disclosure: the practice of privately alerting an operator and its host before publishing details of a leak, as the researchers did here.
  • Phishing: fraud that uses leaked personal details to send convincing fake messages aimed at stealing credentials or money.

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, were accurate to the best of our knowledge as of November 2026, and may change. Nothing here is a finding of wrongdoing against any named party. Gamble responsibly.

Leave a Comment
TOP PRESS RELEASE