Breach Disclosure: 8Tracks

In June 2017, playlist tracking service 8Tracks suffered a data breach. In the disclosure written by the company, they believe that one of their developer's Github accounts was compromised which led to the breach. They cited the reason for the compromise as a "lack of 2-factor authentication". The breach contained approximately 18 million rows of usernames, emails and salted SHA-1 passwords.

Recommendations

If not already enabled, turn on the compromised credentials rule for all relevant entities and ensure relevant emails are entered for those entities, or reach out to [email protected] for assistance
If one of your entities receives an alert, ZeroFOX recommends immediate password changes for the affected account
Enable 2-factor authentication for all of your organizational accounts to help mitigate phishing and credential stuffing attacks
Remain alert to potential spear phishing attacks through email and social media

Details

The breach disclosure did not specifically say what cryptographic hashing algorithm was used to protect user passwords. The company believes that the affected Github account was used to pivot to a backup table that contained the data. It's hard to imagine exactly what happened here, but it sounds like the user account had enough sensitive data to access backup tables, whether it was stored in Github itself or on a server that was not as secure as their production databases.