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

Recent Breaches › Lolzteam Data Breach (2018)

MEDIUM severityConfirmedHow we verify

Lolzteam Data Breach (2018): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·May 13, 2018

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

Lolzteam Data Breach (2018)

Reported May 13, 2018. Approximately 398K people affected.

MEDIUM
Severity
398K
People affected
2
Data types exposed
May 13, 2018
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Lolzteam Data Breach (2018) (reported May 13, 2018) exposed Email addresses and Usernames belonging to roughly 398K 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
MEDIUM severityConfirmed
Contact / identity PII exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Lolzteam Data Breach (2018) breach?
398K 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 May 2018, a data breach at Lolzteam exposed the usernames and email addresses associated with roughly 398,000 accounts. The incident was reported on May 13, 2018, and the exposed records were later shared on a separate hacking forum. For individuals whose details appeared in the data, the exposure creates a lasting record that can be referenced in future targeting attempts.

What happened

The breach occurred at Lolzteam, a Russian hacking forum. Public reporting on the incident states that usernames and email addresses belonging to approximately 398,000 members were obtained and subsequently redistributed. No further technical details about the method of access or the exact timing of the intrusion have been disclosed in available accounts of the event.

How a breach like this happens

Online forums and similar community platforms are frequently targeted because they maintain lists of active user accounts. Unauthorized access can occur through compromised administrator credentials, unpatched server software, or direct database extraction. Once obtained, the resulting files are sometimes traded or posted on other forums, extending the period during which the information remains available.

About Lolzteam

Lolzteam operated as a Russian-language forum focused on hacking-related discussions. Organizations of this type collect basic registration information to manage user accounts and maintain community access controls. A breach at such a site is consequential because the membership often includes individuals who are already attentive to security topics, yet the exposed contact details can still be used to reach them through unrelated channels.

The information in question

The records reported as exposed consist of email addresses and usernames. No other categories of data have been confirmed in public descriptions of the incident. While forums of this kind commonly store additional fields such as registration dates or IP addresses, the precise contents of the Lolzteam dataset remain limited to the two data types named in reports.

What's at stake

Exposed email addresses can be added to lists used for phishing or spam campaigns. When an address is already linked to a username from a hacking forum, the combination may increase the likelihood of targeted messages that reference that context. For the organization, the incident highlights the difficulty of protecting member data on platforms that attract repeated scrutiny from other actors in the same online spaces.

If your data was in this breach

Individuals can review account activity on any services where the exposed email address is used and consider changing passwords if reuse is a concern. Monitoring for unusual login attempts or unsolicited messages that reference the forum can provide early indication of follow-on activity. Readers may also run a free exposure scan of their email address against known breach datasets to check for additional appearances of the same information.

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

CompanyLolzteam security record
74/100
DoxxScan™ · Moderate doxx risk
B+ 85Strong record

1 reported incident on record.

See Lolzteam’s full breach history →

More recent breaches

Data & Leads Data Breach (2018)November 14, 2018Adapt Data Breach (2018)November 5, 2018Elasticsearch Instance of Sales Leads on AWS Data Breach (2018)October 29, 2018GoldSilver Data Breach (2018)October 21, 2018

Latest breaches

Read GalaxyWarden’s full analysis of the Lolzteam Data Breach (2018) →

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