Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
Breach occurred 2012-07-01Verifieddisqus.com
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.
Data exposed
Frequently asked questions
The Disqus data breach occurred on July 1, 2012. It was added to Have I Been Pwned's breach catalog on October 6, 2017.
17,551,044 accounts were affected by the Disqus data breach, according to Have I Been Pwned's records.
The Disqus breach exposed the following data types: Email addresses, Passwords, Usernames.
Yes. Have I Been Pwned has verified the Disqus breach, meaning there's confirmed evidence the exposed data is genuine and tied to real accounts.
Use KazaSec's free Email Breach Checker (/tools/breach-check) to check whether a specific email address has surfaced in the Disqus breach, or any other known breach — the tool never stores what you search.
Our free Email Breach Checker tells you whether a specific email address has surfaced in this breach — or any other known breach — without ever storing what you search.
Check your email →Talk to us about this
We help organizations find and fix the gaps that lead to a breach, before they do.