Breach Database / 8tracks

Yes — 8tracks was breached.

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 JimScott.Sec@protonmail.com and updated in HIBP accordingly.

What data was exposed

What to do right now

  1. Change your password for this service now. And change it anywhere you reused the same password — attackers try leaked passwords on other sites within hours ("credential stuffing").
  2. Turn on two-factor authentication. Even a leaked password is useless against an account protected by a second factor. Prefer an authenticator app over SMS.
  3. Expect convincing phishing emails. Attackers use breached details to write personalized emails. Be suspicious of any message referencing this service.
  4. Check your other accounts on Have I Been Pwned. Your email address may appear in other breaches you don't know about yet.
  5. Monitor the apps you use going forward. Clearly watches the breach record for the companies behind your apps and alerts you the moment one appears.

Breach data from Have I Been Pwned. Listing here means the service appears in the public breach record — not that your personal data was affected.