Breach Intelligence

2,850

Total breached databases

The Touchntell.com.au 2021 breach has been documented in our records, but additional information is not yet available. When the breach is imported, you will be able to search against it. For now, you can check if your data appears in other breaches.

  • Data: The data involved in the Touchntell.com.au 2021 security incident has not been specified. We are monitoring for reliable updates and will publish them here.
  • Imported:
  • Number of lines: 1,772,536
  • Size: 166.01 MB
  • Passwords: ?

At present, no extended description exists for the Vimemc.ru incident. This entry is included so you are aware of its existence. Verification against this breach will be possible in the future. Meanwhile, you can check other breaches for your information.

  • Data: It is unclear which categories of data were compromised in the Vimemc.ru breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 768,538
  • Size: 124.68 MB
  • Passwords: ?

The Lavaguden.ru 2019 breach has been recorded in our database, but additional details are not yet confirmed. When more data becomes available, you will be able to verify your exposure. In the meantime, you can check our list of other breaches.

  • Data: The data categories affected by the Lavaguden.ru 2019 breach have not been disclosed yet. We will expand this section when details are released.
  • Imported:
  • Number of lines: 15,975
  • Size: 1.78 MB
  • Passwords: ?

At present, no extended description exists for the Xakepok.su 2011 incident. This entry is included so you are aware of its existence. Verification against this breach will be possible in the future. Meanwhile, you can check other breaches for your information.

  • Date: 2011
  • Domain: xakepok.su
  • Category: Hacking
  • Records Announced: 31,867
  • Data: It is unclear which categories of data were compromised in the Xakepok.su 2011 breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 416,077
  • Size: 285.96 MB
  • Passwords: vBulletin
  • Cracked: 0%

We do not yet have a full description for the Cirp-cms2016.org 2019 breach. Our goal is to track incidents like this so that users can stay informed. You will be able to check if your information is included when this breach is processed. Until then, you can check other breaches in our database.

  • Data: It is not yet known which data types were exposed in the Cirp-cms2016.org 2019 incident. This page will be updated as more details are verified.
  • Imported:
  • Number of lines: 1,041,450
  • Size: 636.92 MB
  • Passwords: ?
In July 2019, Club Penguin Rewritten (CPRewritten), an independent recreation of Disney’s Club Penguin game, allegedly suffered a data breach. This incident followed an earlier breach that had affected 1.7 million accounts and reportedly exposed 4 million unique email addresses. Among the compromised data were usernames, IP addresses, and passwords stored as bcrypt hashes.
  • Data: Email Addresses IP Addresses Passwords Usernames
  • Imported:
  • Passwords: BCrypt
  • Cracked: 0%
In October 2021, a database backup taken from the 3D model sharing service Thingiverse began extensively circulating within the hacking community. Dating back to October 2020, the 36GB file contained 228 thousand unique email addresses, mostly alongside comments left on 3D models. The data also included usernames, IP addresses, full names and passwords stored as either unsalted SHA-1 or bcrypt hashes. In some cases, physical addresses was also exposed. Thingiverse's owner, MakerBot, is aware of the incident but at the time of writing, is yet to issue a disclosure statement.
  • Data: Birthdates Email Addresses IP Addresses Names Passwords Physical Locations Usernames
  • Imported:
  • Number of lines: 255,555,952
  • Size: 36.14 GB
  • Passwords: BCrypt, SHA-1
  • Cracked: 0%

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.