LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › SubaGames Data Breach (2016)

CRITICAL severityConfirmedHow we verify

SubaGames Data Breach (2016): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·November 1, 2016

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

SubaGames Data Breach (2016)

Reported November 1, 2016. Approximately 6.1M people affected.

CRITICAL
Severity
6.1M
People affected
3
Data types exposed
November 1, 2016
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The SubaGames Data Breach (2016) (reported November 1, 2016) exposed Email addresses, Passwords and Usernames belonging to roughly 6.1M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the SubaGames Data Breach (2016) breach?
6.1M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

People who registered accounts with SubaGames may find their email addresses, usernames, and passwords among records exposed in a 2016 incident that involved 6.1 million unique email addresses. The exposure of login credentials creates a direct risk that the same details could be tested against other services, especially where users reused passwords. The incident was reported on November 1, 2016. Public records state that the breach affected 6.1 million unique email addresses along with usernames and passwords. Most passwords appeared in plain text in the circulated file after they had been cracked from salted MD5 hashes. The data set was later provided to Have I Been Pwned by dehashed.com. No further details on the method of initial access or the exact timing of the intrusion have been disclosed.

Breaking down the breach

The reported facts center on the scale of exposed email addresses and the condition of the password data. Salted MD5 hashing was in use at the time, yet the hashes were subsequently cracked, allowing the passwords to circulate in readable form. No information has been released about the number of records that remained uncracked or about any additional data fields that may have been present in the original database.

How a breach like this happens

Incidents involving account databases often begin with unauthorized access to an application or server that stores user credentials. Once inside, attackers can copy the stored hashes. When those hashes use older algorithms such as MD5, even with salting, offline cracking tools can recover many passwords if the original values are short or commonly used. The resulting plain-text credentials are then traded or published, extending the impact beyond the original service.

About SubaGames

SubaGames is a developer and publisher of online games. Organizations in this sector maintain user accounts to manage logins, in-game purchases, and community features. The data they hold therefore centers on identifiers and authentication details rather than extensive personal or financial records. A breach at such a company is consequential because account credentials are frequently reused across unrelated services.

The information in question

The breach record names three categories of data: email addresses, usernames, and passwords. The passwords were stored as salted MD5 hashes that were later cracked for most entries. No other data types are confirmed in the available reporting. Organizations of this type commonly store only the information required to operate player accounts, yet the precise contents of any individual record remain unconfirmed beyond the three fields listed.

Why it matters

Exposed email addresses and usernames can be used for targeted phishing or to link activity across platforms. When passwords are also available in plain text, the immediate concern is credential-stuffing attempts against other sites. For the organization, the incident highlights the long-term consequences of retaining older hashing methods once a data set leaves its control.

If your data was in this breach

Review any SubaGames account still active and change its password to a unique value. Enable two-factor authentication on that account and on any other service that uses the same email address. Check whether the same password appears elsewhere by running a free exposure scan of the email address against known breach data. Monitor login notifications from other services for unexpected activity.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanySubaGames security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See SubaGames’s full breach history →

More recent breaches

Anti Public Combo List Data Breach (2016)December 16, 2016Ethereum Data Breach (2016)December 16, 2016PayAsUGym Data Breach (2016)December 15, 2016MrExcel Data Breach (2016)December 5, 2016

Latest breaches

Read GalaxyWarden’s full analysis of the SubaGames Data Breach (2016) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram