Ongab Data Breach
The 2017 Ongab data breach occurred in June 2017 when the user and community database of Ongab (ongab.ru), a prominent Russian gaming social network, MMORPG news portal, and gaming guide aggregator founded in the 2010s, was breached and distributed across hacking communities.
Exposed Data Types
9- Email addresses
- Usernames
- Passwords
- IP addresses
- Dates of birth
- Phone numbers
- Social media profiles
- Instant messenger identities
- Financial identifiers
About This Breach
What information was affected in the Ongab incident?
The compromised SQL/CSV exports (db_users.csv, ongab_users.csv, dota2_users.csv, ongab_users_data.csv) contain in-depth player dossiers. Impacted records for 83,992 unique accounts encompass:
- Account Profiles: Gamer handles (nick) and birthdates (bdate).
- Contact Credentials: Canonical validated email addresses and telephone numbers.
- Authentication Secrets: Passwords stored as MD5 cryptographic hashes.
- Network Identifiers: Member IP addresses and session tokens.
- Social Media & Messenger Handles: VKontakte profile IDs and access tokens, Facebook IDs, Skype usernames, and ICQ numbers.
- Financial Identifiers: WebMoney WMR wallet addresses and Yandex Money account IDs used for gaming transactions.
How many accounts were affected?
Rigorous RFC canonical parsing and deduplication across 285,394 total user records confirmed 83,992 unique valid email addresses.
Technical analysis and security risks
The compromise of unsalted MD5 password hashes allows rapid offline brute-force and dictionary attacks. The cross-referencing of social network IDs (VK/Facebook), gaming forum handles, and payment wallets exposes victims to identity deanonymization, targeted spear-phishing, and gaming account takeover.
Recommended actions for affected users
Gamers previously registered on Ongab.ru should:
- Immediately update passwords on any platforms sharing identical credentials.
- Enable two-factor authentication (2FA) and gaming authenticators (such as Steam Guard) across all sensitive 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
