Skip to content
Back to Blog
high severity July 01, 2012 · 1 min read

Disqus Data Breach (2012)

If you are a customer of Disqus, here’s what’s now in circulation.

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.

Disqus Data Breach (2012)

What the free scan actually returns

Sample resultyou@email.comIllustrative — not a real person

Found on people-search siteswe remove these

These listings are live, public, and legal to remove — and removing them is what we do.

value redacted in this sampleage, relatives, address historySpokeo
value redacted in this samplephone, household, property recordsBeenVerified
value redacted in this sample582 companies checked

Found in breach recordsverifiedreported — unverified

Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.

verifiedvalue redacted in this samplepassword + phone · 2024telecom breach
unverifiedvalue redacted in this sampleclaimed in ransomware listing · 2026leak-site claim

Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.

Were you a Disqus customer?
Disqus is one listing. Your email is probably in others.
17.6M accounts were exposed here. Check whether yours is one — and find every other leak tied to the same address, in about 15 seconds. No account, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

Report details & sourcing

Severity High contact details only, none of them permanent
Disclosed July 01, 2012
Last reviewed July 22, 2026
Affected 17.6M
Data exposed Email addressesPasswordsUsernames
By GalaxyWarden Threat Research · Editorial & sourcing standards
Editorial & sourcing policy
GalaxyWarden is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data. Breach information is compiled from publicly accessible sources and threat-intelligence platforms, and is reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — see our content & takedown policy or write to support@galaxywarden.com.
Sources: Have I Been Pwned
Share this Post on X Reddit Email

Related breaches

critical May 05, 2012

LinkedIn — 164 Million Accounts, Unsalted SHA-1, Four Years in the Dark (2012)

Hacked in 2012, sold in 2016. LinkedIn stored passwords as unsalted SHA-1 and the vast majority were…
critical January 29, 2026

Match Group (Tinder, Hinge, OkCupid) Data Breach — January 2026

ShinyHunters claimed responsibility for stealing over 10 million Match Group user records in early 2…
critical January 23, 2026

149 Million Credential Mega-Exposure — January 2026

Security researchers discovered a publicly exposed 96 GB database with 149 million unique logins cov…