16,952,675
Records Exposed
Jul 2012
Date of Breach
Database
Breach Type
Jul 2022
Added to Database
About This Breach
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 27.8 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 Data Types
Country
United States
Language
English
Password Storage
SHA1, Plaintext
Category
Hosting, IT Services
Indexed On
Jul 25, 2022
Breach Type
Database
What Should You Do?
Get Full Breach Details with LeakedSource Pro
Sign up for a LeakedSource Pro account to see exactly what data was exposed in this breach and get real-time notifications when your information appears in new breaches.
Sign Up for Pro- Change your password immediately on Disqus and any other site where you used the same password. Use a unique, strong password for each account.
- Watch for phishing emails targeting your inbox. Attackers may use your exposed email address to send convincing scam messages.
- Enable two-factor authentication (2FA) on all important accounts to add an extra layer of security.
- Use a password manager to generate and store unique, strong passwords for every account.
Were You Affected by This Breach?
Enter your email below to instantly check if your data was compromised in the Disqus breach and 12,000+ other known breaches.
