Disqus Data Breach History

This page tracks the Disqus data breach history and cybersecurity incidents affecting Disqus. BreachHistory currently indexes 3 publicly disclosed or catalogued incidents spanning 2012 through 2017, with approximately 52.5 million records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.

The Disqus breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed.

Largest Disqus Data Breaches

The largest indexed incidents include the 2017 Disqus — 17.5M accounts, the 2017 — Disqus: Hackers stole 17, 17.5M records, and the 2012 — Disqus: hackers 17, 17.5M records. Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by Disqus or a regulator. Below is the list of large data breaches:

• 2017 2017 Disqus — 17.5M accounts — about 17.5M records exposed · Catalogued incident
• 2017 2017 — Disqus: Hackers stole 17, 17.5M records — about 17.5M records exposed · Catalogued incident
• 2012 2012 — Disqus: hackers 17, 17.5M records — about 17.5M records exposed · Catalogued incident

What Information Was Exposed?

Depending on the incident, exposed data may include email addresses, passwords and login credentials, names, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.

Disqus Data Breach 2026

At the time of this update, no Disqus data breach has been catalogued for 2026. New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.

What To Do If You Were Affected

If you believe your account may have been involved in a Disqus data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.

This Disqus breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.