All Breaches
March 16, 2018 Verified Gaming

Neverendless-WoW Data Breach

The 2018 Neverendless-WoW data breach occurred in March 2018 when the player database of Neverendless-WoW (neverendless-wow.com), one of the oldest and most established World of Warcraft: Wrath of the Lich King (3.3.5a) private server networks, was breached and published on online hacking communities.

304.6 Thousand
Reported Records
4
Data Types
High
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

4
  • Email addresses
  • Usernames
  • Passwords
  • IP addresses

About This Breach

What information was affected in the Neverendless-WoW incident?

The compromised user export (neverendless-wow.com.csv) contains player registration and authentication records. Impacted records for 304,550 unique players encompass:

  • Account Identifiers: Player usernames and internal user IDs (userid).
  • Contact Credentials: Canonical active email addresses and original registration email addresses.
  • Authentication Secrets: Passwords hashed with SHA-1 and bcrypt ($2y$).
  • Network Identifiers: Player connection IP addresses.

How many accounts were affected?

Rigorous RFC canonical parsing and deduplication across 341,642 player database records confirmed 304,550 unique valid email addresses.

Technical analysis and security risks

The presence of legacy SHA-1 password hashes enables straightforward offline cracking. Threat actors actively cross-reference private gaming server databases against official Blizzard Battle.net, Steam, and Discord accounts using credential stuffing techniques to hijack valuable gaming profiles.

Recommended actions for affected users

Gamers who played on Neverendless-WoW should:

  • Immediately change passwords on any current gaming or email services where the same credentials may have been reused.
  • Enforce two-factor authentication (such as Blizzard Mobile Authenticator) across all gaming and personal accounts.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information