Breach Intelligence

2,852

Total breached databases

In October 2017, the genealogy website MyHeritage suffered a data breach. The incident was reported 7 months later after a security researcher discovered the data and contacted MyHeritage. In total, more than 92M customer records were exposed and included email addresses and salted SHA-1 password hashes. In 2019, the data appeared listed for sale on a dark web marketplace (along with several other large breaches) and subsequently began circulating more broadly.
  • Data: Email Addresses Passwords
  • Records: 92,284,362
  • Lines: 92,284,487
  • Size: 7.61 GB
  • Passwords: SHA-1 Salted
  • Cracked: 94%
In April 2019, the PDF management service Lumin PDF suffered a data breach. The breach wasn't publicly disclosed until September when 15.5M records of user data appeared for download on a popular hacking forum. The data had been left publicly exposed in a MongoDB instance after which Lumin PDF was allegedly been "contacted multiple times, but ignored all the queries". The exposed data included names, email addresses, genders, spoken language and either a bcrypt password hash or Google auth token.
  • Data: Email Addresses Genders Languages Names Passwords Security Credentials Usernames
  • Records: 24,385,902
  • Lines: 24,386,039
  • Size: 4.07 GB
  • Passwords: BCrypt
  • Cracked: 20%
In 2017, leotvhd.com experienced a data breach that exposed approximately 128,585 user records. The compromised data included email addresses and passwords hashed using the MD5 algorithm without salts. The use of unsalted MD5 increased the risk of password cracking and unauthorized account access.
  • Data: Email Addresses Passwords
  • Records: 128,576
  • Lines: 128,585
  • Size: 7.19 MB
  • Passwords: MD5
  • Cracked: 0%
In September 2019, game developer Zynga (the creator of Words with Friends) suffered a data breach. The incident exposed 173M unique email addresses alongside usernames and passwords stored as salted SHA-1 hashes.
  • Data: Email Addresses Passwords Phone Numbers Usernames
  • Records: 213,970,829
  • Lines: 216,595,932
  • Size: 81.33 GB
  • Passwords: Rails
  • Cracked: 32%
In December 2018, the digital mall Wanelo reportedly suffered a data breach affecting 23 million users. Among the compromised data were email addresses, IP addresses, names, physical locations, and passwords stored as either MD5 or bcrypt hashes.
  • Data: Email Addresses IP Addresses Names Passwords Physical Locations
  • Records: 23,188,882
  • Lines: 23,188,883
  • Size: 1.75 GB
  • Passwords: BCrypt, MD5
  • Cracked: 13%
In December 2018, the data science website DataCamp suffered a data breach of records dating back to January 2017. The incident exposed 760k unique email and IP addresses along with names and passwords stored as bcrypt hashes. In 2019, the data appeared listed for sale on a dark web marketplace (along with several other large breaches) and subsequently began circulating more broadly.
  • Data: Email Addresses Geographic Locations IP Addresses Names Passwords
  • Records: 760,610
  • Lines: 760,642
  • Size: 250.66 MB
  • Passwords: BCrypt
  • Cracked: 24%
In 2014, the private RuneScape server Soulsplit suffered a data breach, exposing users' email addresses, IP addresses, usernames, hashed passwords, and social media profiles.
  • Data: Email Addresses IP Addresses Passwords Social Profiles Usernames
  • Records: 227,180
  • Lines: 227,230
  • Size: 66.33 MB
  • Passwords: SHA-1
  • Cracked: 99%

Frequently Asked Questions

A data breach is unauthorized access to data (often involving account takeover, malware, or misconfigured infrastructure). A data leak is exposure of data due to mistakes like public cloud storage, open databases, or accidental publishing. A database dump is a packaged dataset that may come from a breach, leak, scraping, or aggregation.

Change passwords for any affected accounts immediately, prioritizing email, banking, and any account that shares the same password. Enable multi-factor authentication wherever possible. Monitor your accounts for suspicious activity and consider placing a fraud alert or credit freeze if financial data was exposed.

Start with containment and verification: confirm what data was exposed, identify the entry point, rotate credentials (especially SSO, VPN, email), and enforce MFA. Then investigate affected systems, notify stakeholders as required, and harden controls to prevent recurrence. A structured incident response plan helps keep the work measurable and compliant.

Dark web monitoring helps you spot exposure signals early — before stolen data is widely reused for account takeover or targeted attacks. Monitoring complements vulnerability management by revealing when attackers already have leverage. Pair it with continuous attack surface monitoring and strong Asset Discovery to reduce blind spots.

Not always. Some datasets are old, incomplete, or derived from third parties. However, any exposure increases risk because credentials and personal data can be reused indefinitely. Treat it as a priority signal: rotate credentials, enforce MFA, review suspicious logins, and audit the systems that could have produced the data.

SynScan helps you connect the dots between attack surface exposure, vulnerabilities, and breach signals so you can prioritize remediation and reduce the chance of repeat incidents.