Back to Radar
8T

8tracks

High

8Tracks faced a breach in June 2017, exposing emails and password hashes.

Records exposed
17,979,961 records
Breach date
Breach Jun 27, 2017
Last update
Updated Aug 25, 2019

What data was exposed?

Fields reported as compromised in this breach record.

Email addressesPasswords

Why does this breach matter?

In-depth analysis of the breach and its implications.

In June 2017, the digital platform 8Tracks, known for playlist sharing, experienced a security breach affecting approximately 18 million user accounts. The breach occurred due to unauthorized access via an employee's GitHub account that was not secured with two-factor authentication. As a result, email addresses and password hashes (for users not utilizing alternative login methods) were exposed.

Impact Analysis

Understanding the scope and consequences of this breach.

User Impact
Exposed email and password combinations could lead to account compromise.
Business Impact
Reputation damage and potential legal consequences.
Affected Sectors
  • Technology
  • Music Streaming
Geographic Impact
  • Global

What You Should Do

Recommended actions to take in response to this breach.

If You Were Affected

  • Change passwords for accounts associated with the breached email.
  • Enable multi-factor authentication on all services.

Preventive Measures

  • Utilize multi-factor authentication.
  • Educate employees on secure credential practices.

Frequently Asked Questions

Common questions about this breach and what it means for you.

The breach capitalized on insecure API credentials in GitHub.