← All datasets

spacetimestudios.com

Apr 1, 2021

7,793,124
Records
2
Files
May 30, 2026
Added

In April 2021, US-based game development studio Spacetime Studios suffered a data breach affecting approximately 7.8 million user accounts. The breach was carried out by threat actor @donjuji using a multi-stage attack chain involving Local File Inclusion, Log Poisoning for Remote Code Execution, AWS credential theft via SSRF, and multiple pivots through the internal network exploiting a vulnerable Atlassian instance. Exposed data includes email addresses, first and last names, bcrypt-hashed passwords (cost factor 6), account IDs, registration timestamps, and deletion status.

Data found in this dataset

EmailFirst nameLast nameskip

Search this dataset

Scoped to this dataset. Fill any combination — results match if any field hits.

Source files

Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.

SpacetimeStudios__Info.txt
8 columns8 rows

File structure

Source columnMapped fieldConfidenceLLM assessment
0skiphighaccount_id is an internal UUID identifier
1emailhighcolumn named 'email', values contain @ symbol and valid email domains
2firstNamehighcolumn named 'first_name', values are personal given names
3lastNamehighcolumn named 'last_name', values are personal family names
4skiphighdeleted is a boolean flag, non-PII account status indicator
5skiphighregistration_time is a timestamp, not date of birth
6skiphighverification_time is a timestamp, not date of birth
7passwordhighcolumn named 'password', values are bcrypt hashes ($2a$06$ format with cost factor 6 as documented in breach)

Notes: SQL dump from Spacetime Studios breach (April 2021). Table: registered_account. Contains 7.8M user records with bcrypt-hashed passwords. No DOB, SSN, phone, address, or other PII fields present in this table structure.

SpacetimeStudios__data__spacetimestudios_bcrypt_8m__registered_account.csv
8 columns7,793,116 rows

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] header 'account_id', values are UUIDs — internal account identifiers, not usernames
1emailhigh[1] header 'email', values are email addresses with @ symbols
2firstNamehigh[2] header 'first_name', values are common given names (mon, sam, benny, etc.)
3lastNamehigh[3] header 'last_name', values are surnames (mon, estassi, bu, paclik, etc.)
4skiphigh[4] header 'deleted', boolean flag (f/t) indicating deletion status — internal flag, not PII
5skiphigh[5] header 'registration_time', ISO 8601 timestamps — metadata, not PII
6skiphigh[6] header 'verification_time', ISO 8601 timestamps (mostly empty) — metadata, not PII
7passwordhigh[7] header 'password', values are bcrypt hashes ($2a$06$...) as noted in breach context — password hashes are still passwords

Notes: Spacetime Studios breach — 8 columns total, 3 contain PII (email, first_name, last_name), plus 1 password hash column. Columns 0, 4, 5, 6 are internal metadata/flags. All PII fields are mapped.

spacetimestudios.com. Shadow Identity