All Breaches
August 17, 2010 Verified Gaming

Totaljerkface Data Breach

The 2010 Totaljerkface data breach occurred in August 2010 when the member database of indie game studio and web portal Totaljerkface (totaljerkface.com), the creators of the iconic ragdoll physics game Happy Wheels developed by Jim Bonacci, was compromised and published online.

187 Thousand
Reported Records
7
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

7
  • Email addresses
  • Usernames
  • Passwords
  • IP addresses
  • Geographic locations
  • Genders
  • Website activity

About This Breach

What information was affected in the Totaljerkface incident?

The leaked member dump (totaljerkface-08-17-2010-users.txt) contained user registrations dating from the inception of Happy Wheels. The exposure impacts 186,950 unique gamer accounts, revealing:

  • Account Identifiers: Player usernames and declared gender.
  • Contact Credentials: Canonical email addresses.
  • Authentication Data: Passwords hashed using bcrypt ($2y$05$ cost factor).
  • Network Logs: User registration and login IP addresses.
  • Geographic Identifiers: Two-letter country geographic location codes.
  • Website Activity: Personal homepage URLs submitted in forum profiles.

How many accounts were affected?

Rigorous RFC canonical parsing and deduplication across 188,057 member rows confirmed 186,950 unique valid email addresses.

Technical analysis and security risks

The dump included records for studio founder Jim Bonacci and early Happy Wheels community participants. While bcrypt provided sound cryptographic protection for password hashes, the clear association between usernames, IP addresses, country locations, and verified emails exposed users to credential stuffing and cross-platform profiling.

Recommended actions for affected users

Players who held accounts on Totaljerkface should:

  • Ensure their passwords on modern gaming and email services are distinct and not reused from legacy accounts.
  • Enable two-factor authentication (2FA) wherever available.

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