All Breaches
September 1, 2019 Unverified Gaming

R2Games 2019 Alleged Data Exposure

The 2019 R2Games data breach occurred in September 2019 when the official vBulletin community forum database of global free-to-play MMO publisher R2Games (r2games.com) was compromised and leaked online.

3.7 Million
Email Identifiers
6
Data Types
Critical
Exposure Scope
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

6
  • Email addresses
  • Usernames
  • Passwords
  • IP addresses
  • Dates of birth
  • Historical logins

About This Record

What information was compromised in the R2Games 2019 incident?

The leaked forum database dump encompasses 3,851,577 registered user records from the vb_user table. Verified data classes include:

  • Account Identifiers: Community usernames, user titles, and forum member IDs.
  • Security Credentials: vBulletin password hashes with cryptographic salts (MD5 and Blowfish algorithms).
  • Contact Details: Verified player email addresses.
  • Network & Temporal Metadata: Registration and last activity IP addresses, birth dates, and account timestamps.

How many accounts were affected?

Standardized RFC 5322 ASCII canonical verification confirmed 3,729,241 unique valid email addresses across 3,851,577 forum accounts.

Security advisory & personal identity protection

The combination of usernames, salted password hashes, and email addresses presents severe risks of credential stuffing and unauthorized account takeover across shared gaming services. Affected individuals should:

  • Immediately update passwords on any service where forum credentials may have been reused.
  • Implement multi-factor authentication (MFA/2FA) on critical online and gaming 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