Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Clash of Kings Forum Breach Exposes 1.6 Million User Credentials and IP Addresses

In July 2016 the Clash of Kings forum was breached, leaking over 1.6 million usernames, emails, IPs and MD5‑hashed passwords. Weak credential storage triggers immediate control‑assurance concerns for any service handling user logins.

LiveThreat™ Intelligence · 📅 October 08, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
haveibeenpwned.com

Clash of Kings Forum Breach Exposes 1.6 Million User Credentials and IP Addresses

What Happened — In July 2016 the online forum for the game Clash of Kings was compromised, leaking 1,604,957 user records. Exposed data included usernames, email addresses, IP addresses and passwords stored as unsalted MD5 hashes. The breach details were disclosed via Have I Been Pwned, sourced from dehashed.com.

Why It Matters for Trust & Control Assurance

  • Demonstrates the risk of weak credential storage – a control‑area that continuous assurance programs must monitor and evidence.
  • Highlights the need for robust authentication controls (strong hashing, salting, MFA) to satisfy multiple framework objectives in a single control.
  • Provides a real‑world example where lack of proper credential protection can trigger regulatory scrutiny and damage trust.

Who Is Affected – Gaming platforms, online community forums, and any SaaS service handling user credentials.

Recommended Actions

  • Replace MD5 hashes with salted, computationally‑hard algorithms (e.g., bcrypt, Argon2).
  • Enforce MFA for all user accounts where feasible.
  • Conduct a credential‑storage audit and map findings to your control‑assurance framework.
  • Implement continuous monitoring for credential exposure and maintain a defensible audit trail.

Source: Have I Been Pwned – Clash of Kings breach

Technical Notes

  • Attack vector unknown; breach likely stemmed from inadequate password hashing and possible server compromise.
  • Passwords were stored as raw MD5 hashes without salting, making them trivially crackable.
  • Data types exposed: email addresses, IP addresses, usernames, password hashes.

Source: Same as above

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/ClashOfKings ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Could you prove your access controls held up here?

Credential and access failures map directly to identity and access-control requirements in every major framework. The Verisq AI Trust Operations platform shows where your evidence is thin before an auditor — or an attacker — finds out.

Explore the Verisq AI Trust Operations platform →