What was exposed, when it happened, and which databases confirm it.
- accounts
- 722,860
- Breached
- July 1, 2024
- Last Update
- September 30, 2024
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
What happened
In September 2024, data from the ticketing service Central Tickets was publicly posted to a hacking forum. The data suggests the breach occurred several months earlier and exposed 723k unique email addresses alongside names, phone numbers, IP addresses, purchases and passwords stored as unsalted SHA-1 hashes.
Compromised Info
- Device information
- Email addresses
- IP addresses
- Names
- Passwords
- Phone numbers
- Purchases
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- LeakCheck— linked via automatic string matching
- HIBP
FAQ
What was leaked in the CentralTickets breach?
The CentralTickets breach exposed: Device information, Email addresses, IP addresses, Names, Passwords, Phone numbers, and Purchases.
When did the CentralTickets breach happen?
The CentralTickets breach was disclosed on July 1, 2024 and affected 722,860 records.
Am I affected by the CentralTickets breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the CentralTickets leak.