Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Unigame Breach Exposes 844k Email Addresses and Password Hashes

In December 2019 the defunct gaming site Unigame suffered a breach that released 843,696 email addresses and salted MD5 password hashes. The incident highlights the need for strong credential‑storage controls and continuous monitoring to satisfy audit‑readiness requirements.

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

Unigame Breach Exposes 844 k Email Addresses and Password Hashes

What Happened – In December 2019 the now‑defunct gaming site Unigame (operator of Hunter Online) suffered a data breach. A dump of 843,696 user records—including email addresses and salted MD5 password hashes—was later redistributed as part of a larger data corpus.

Why It Matters for Trust & Control Assurance

  • Credential exposure is the exact scenario a continuous control‑assurance program seeks to prevent: strong password‑hashing, credential‑access monitoring, and evidence of remediation.
  • Demonstrating robust identity‑and‑access controls (e.g., migration to Argon2 or bcrypt, regular credential‑reuse checks) provides defensible audit evidence across frameworks such as NIST CSF 2.0.
  • Ongoing third‑party monitoring of credential‑leak feeds helps maintain a real‑time view of exposure risk and supports incident‑response readiness.

Who Is Affected – Online gaming platforms, digital entertainment services, and any organization that stored user credentials with weak hashing algorithms.

Recommended Actions

  • Inventory all password‑storage mechanisms; replace MD5‑based hashes with memory‑hard algorithms (bcrypt, Argon2).
  • Force password resets for affected accounts and monitor for credential‑stuffing attacks.
  • Incorporate credential‑leak detection into your continuous monitoring stack to generate timely evidence for auditors.

Technical Notes – The breach involved salted MD5 hashes, which are considered cryptographically weak and vulnerable to rainbow‑table attacks. No specific CVE or exploit was disclosed; the breach appears to stem from inadequate password‑storage practices. Source: Have I Been Pwned – Unigame breach

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

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 →