What was exposed, when it happened, and which databases confirm it.
- accounts
- 30,997,416
- Breached
- July 1, 2012
- Last Update
- October 6, 2017
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
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.
Compromised Info
- Email addresses
- Passwords
- Usernames
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- LeakCheck— linked via automatic string matching
- Dehashed— linked via domain matching
- HIBP
FAQ
What was leaked in the Disqus breach?
The Disqus breach exposed: Email addresses, Passwords, and Usernames.
When did the Disqus breach happen?
The Disqus breach was disclosed on July 1, 2012 and affected 17,551,044 records.
Am I affected by the Disqus breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Disqus leak.