All Breaches
January 1, 2021 Unverified Sensitive Record Adult Content

Fortnite Porn 2021 Data Breach Claim

A data-breach claim associated with Fortnite Porn is dated to 2021. The NiamonX incident page reports January 2021 and approximately 76.4 thousand users.

72.6 Thousand
Affected Accounts
3
Data Types
Medium
Exposure Scope
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

3
  • Usernames
  • Hashed passwords
  • Email addresses

About This Record

The 9GHz incident record identifies the target as fortniteporn.org and publishes a claim of 76,469 records, the same SQL filename as the source archive, and matching compressed and expanded sizes. An archived official site page dated 8 January 2021 also establishes the fortniteporn.org identity and a Piwigo platform consistent with the source SQL schema. This evidence shows that the previous fortniteporn.com catalog domain was incorrect.

The sealed archive's main SQL file contains 76,247 piwigo_users rows and an explicitly named mail_address column. Two independent full-dataset parsers produced byte-identical results for 72,840 valid email occurrences; removing one duplicate occurrence left 72,839 unique canonical emails. The earlier import collected email-like tokens from every archive byte and consequently added 106 unauthorized relations; those links were removed without deleting the shared email documents. Only the email column was authorized for import; usernames, password hashes, and every other field were excluded.

The catalog scope of 72,611 accounts, the 9GHz claim of 76,469 records, the 76,247 SQL rows, and the 72,839 source-verified unique email relations are different measures and were not fitted to one another. No matching a public breach source entry or operator incident confirmation was located, so the record remains unverified. An email match alone would not prove that a person held an account or that any other data type co-occurred in the same record.

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