Lizard Squad Data Breach (2015): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Lizard Squad Data Breach (2015) (reported January 16, 2015) exposed Email addresses, Passwords and Usernames belonging to roughly 13K 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.
Breaking down the breach
The reported facts indicate that Lizard Squad launched Lizard Stresser in January 2015 as a paid service for mounting distributed denial-of-service attacks. Within a short period, the service experienced a breach that led to the public release of user account information. The disclosed records covered more than 13,000 accounts and contained email addresses, usernames, and passwords stored without encryption. No further details on the method of access, exact timing of the intrusion, or total volume of records have been confirmed in available reports.
How a breach like this happens
Incidents involving online services that accept payments or store user credentials often begin with an attacker gaining unauthorized entry through weak authentication controls, unpatched software, or compromised administrative accounts. Once inside, an intruder can extract stored data and publish it on public forums or leak sites. When passwords are kept in plain text rather than hashed, the exposed records become immediately usable for further attempts at account takeover on other platforms. The scale of disclosure depends on how many records an attacker locates and chooses to release.
About Lizard Squad
Lizard Squad is a hacker collective that gained public attention for operating tools and services related to network disruption. In this case, the group offered Lizard Stresser as a commercial platform that customers could use to direct traffic floods at chosen targets. Organizations that run such services typically collect user registration details, payment information, and login credentials to manage accounts and process transactions. A breach at one of these services therefore places both the operators and their customers at risk of having their account data circulated without consent.
What was likely exposed
The breach record lists email addresses, usernames, and passwords as the data types released. The passwords were stored in plain text, which means they did not require additional processing to be read. No other categories of information, such as payment card details or personal identifiers beyond usernames and emails, are named in the reported facts. The precise contents of every record remain unconfirmed beyond these fields.
What's at stake
Individuals whose accounts appeared in the disclosure face the possibility that their credentials could be tested against other online services where the same email and password combination was reused. Lizard Squad and any associated operators face reputational damage and potential legal exposure from the release of customer data. Because the service itself facilitated attacks on third-party systems, the breach also drew attention to the broader practice of offering paid disruption tools and the data-handling practices that accompany them.
What to do if you're exposed
Anyone concerned about possible exposure should change passwords on any accounts that share the same credentials listed in the breach, starting with email and any services that hold financial or personal information. Enabling two-factor authentication on remaining accounts reduces the value of a leaked password alone. Readers can run a free exposure scan of their email address against known breach data sets to check whether their information appears in this or other documented incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Trillian Data Breach (2015)QuinStreet Data Breach (2015)Aternos Data Breach (2015)DaniWeb Data Breach (2015)Latest breaches
Read GalaxyWarden’s full analysis of the Lizard Squad Data Breach (2015) →
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.