GGCorp 2022 Data Breach Record

SynScan publishes 2,504,726 records, 2,504,772 lines and 455.97 MB under the same GGCorp label. Unique emails, records and lines are different units; the figures do not prove the same dataset version or coverage and were not fitted to one another. A linked August 13 forum-monitoring post says a vendor added a GGCorp database, but it does not establish the access method, that August 11 was an attack day, or that every listed field occurs in every record.

LeakData's completed historical job imported 2,369,562 email relations from the explicit email column only, 6,768 below a public breach source's unique-email measure. The historical record identifies the source as a pre_ucenter_members SQL table and says usernames, passwords, IPs, salts and authentication fields were not imported. The original SQL/job file, DHT archive and a v3 input manifest are unavailable, so the dataset version, column authority and the differences between both external sources and the local set cannot be re-established from source today.

A private match shows only that the controlled email occurs in this local email subset. It does not establish identity, a GGCorp or MMORPG account, gaming activity, IP or location, a username or password association, or field co-occurrence. The record is treated as sensitive because the source describes password and IP classes. If a password from the relevant period was genuinely reused elsewhere, replacing it with a unique password on those accounts is an appropriate conditional precaution; a hash is not a plaintext password.