What was exposed, when it happened, and which databases confirm it.
- accounts
- 41,236,470
- Breached
- June 27, 2017
- Last Update
- August 25, 2019
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
What happened
In June 2017, the online playlists service known as 8Tracks suffered a data breach which impacted 18 million accounts. In their disclosure, 8Tracks advised that "the vector for the attack was an employee’s GitHub account, which was not secured using two-factor authentication". Salted SHA-1 password hashes for users who didn't sign up with either Google or Facebook authentication were also included. The data was provided to HIBP by whitehat security researcher and data analyst Adam Davies and contained almost 8 million unique email addresses. The complete set of 18M records was later provided by [email protected] and updated in HIBP accordingly.
Compromised Info
- Email addresses
- Passwords
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
- Dehashed— linked via domain matching
- HIBP
FAQ
What was leaked in the 8tracks breach?
The 8tracks breach exposed: Email addresses and Passwords.
When did the 8tracks breach happen?
The 8tracks breach was disclosed on June 27, 2017 and affected 41,236,470 records.
Am I affected by the 8tracks breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the 8tracks leak.