8tracks Data Breach
The 8tracks data breach affected approximately 17,979,961 accounts in June 2017. The confirmed data classes are email addresses and salted SHA-1 password hashes; passwords held by external social-sign-in providers were not stored by 8tracks and are outside this record.
Exposed Data Types
2- Email addresses
- Passwords
About This Breach
A password hash is not a plaintext password, but SHA-1 is weak by current password-storage standards. Reused or similar passwords can create an account-takeover risk, and email addresses can support targeted phishing.
A match means that the email address appears in the verified 8tracks dataset; it does not prove a current account compromise or that every row contained a password hash. Change old reused passwords, review social-login accounts and recovery settings, and never share verification codes.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
