Disqus Data Breach

What happened?

In October 2017, the blog commenting service Disqus announced they'd suffered a data breach . The breach dated back to July 2012 but wasn't identified until years later when the data finally surfaced. The breach contained over 17.5 million unique email addresses and usernames. Users who created logins on Disqus had salted SHA1 hashes of passwords whilst users who logged in via social providers only had references to those accounts.

When did it happen?

The breach date in the public record is July 1, 2012. The record was added to the catalogue on October 6, 2017 and last updated there on October 6, 2017.

What information was reported as exposed?

• Email addresses
• Passwords
• Usernames

These are incident-level categories. The record does not prove that every category was exposed for every affected person.

Who may be affected?

This record may be relevant to people who had an account or other relationship with Disqus or used disqus.com around July 1, 2012. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.

What should you do?

Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.