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

Recent Breaches › Epic Games Data Breach (2016)

HIGH severityConfirmedHow we verify

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

RBRecent Breaches Breach Intelligence·August 11, 2016

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

Epic Games Data Breach (2016)

Reported August 11, 2016. Approximately 252K people affected.

HIGH
Severity
252K
People affected
3
Data types exposed
August 11, 2016
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Epic Games Data Breach (2016) (reported August 11, 2016) exposed Email addresses, Passwords and Usernames belonging to roughly 252K 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
HIGH severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Epic Games Data Breach (2016) breach?
252K 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.

In August 2016, Epic Games disclosed that its online forum had been compromised, resulting in the exposure of 252,000 user accounts. The incident was reported on August 11, 2016, and involved usernames, email addresses, and salted MD5 hashes of passwords. Public records indicate the breach occurred through a SQL injection vulnerability in the forum software. This event remains relevant because online platforms that store user credentials continue to face similar technical exposures, and the data from incidents of this age still circulates in later compilations.

Inside the incident

The breach affected the Epic Games forum and was reported in August 2016. Records state that 252,000 accounts were exposed. The data included usernames, email addresses, and salted MD5 hashes of passwords. The reported summary attributes the access to a SQL injection vulnerability in vBulletin. No further details on the precise timing of the intrusion, the number of files accessed, or the method of initial entry beyond the alleged vulnerability have been disclosed in available records.

How a breach like this happens

SQL injection occurs when an application fails to properly validate or sanitize input supplied through web forms or URLs. An attacker can then craft queries that cause the database to return or alter records it was not intended to expose. Forum software such as older versions of vBulletin has historically been targeted because it accepts user input in multiple locations and, when unpatched, can allow direct database interaction. Once initial access is obtained, an attacker may extract tables containing account information without needing elevated system privileges.

Who is Epic Games?

Epic Games develops and publishes video games and provides related online services, including forums for community discussion. Organizations in this sector maintain user accounts that link email addresses, usernames, and authentication data to enable login, support, and community features. A breach at such a company is consequential because the accounts often overlap with payment or game-progress records, even when those additional fields are not confirmed as exposed in a given incident.

The information in question

The facts name three categories of data: usernames, email addresses, and salted MD5 hashes of passwords. No other data types are listed in the available records. Organizations of this type commonly store additional profile details, purchase histories, or linked game accounts, but the exact contents of the 2016 incident remain unconfirmed beyond the three fields reported.

Why it matters

Email addresses paired with usernames can facilitate targeted phishing or account-recovery attempts on other services where the same credentials are reused. Salted password hashes raise the difficulty of reversal compared with unsalted hashes, yet offline cracking remains possible for weak or reused passwords. For the organization, the incident required notification, investigation, and remediation of the underlying vulnerability, along with any subsequent monitoring of credential misuse.

If your data was in this breach

Change the password on the affected Epic Games account and on any other service where the same password was used. Enable multi-factor authentication where available. Review recent account activity for signs of unauthorized access. Readers can run a free exposure scan of their email address against known breach data sets to determine whether their information appears in this or other documented incidents.

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

CompanyEpic Games security record
74/100
DoxxScan™ · Moderate doxx risk
B- 78Above-average record

1 reported incident on record.

See Epic Games’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 Epic Games 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