Breach Intelligence

2,850

Total breached databases

Details about the Sharewood.biz 2013 breach remain unavailable. Once it is imported, you will be able to check if your data was affected. Until then, you may search through other breaches to stay informed.

  • Data: At this stage, the exact nature of the compromised information in the Sharewood.biz 2013 breach is unknown. Updates will be provided as they are verified.
  • Imported:
  • Number of lines: 1,371,641
  • Size: 437.15 MB
  • Passwords: ?

Details about the Verified.cash 2019 data breach are currently limited. This entry was added to our database to help raise awareness, and we will update this page with more information as it becomes available. You will be able to check if your data appears in this breach once it is fully imported. Meanwhile, you can see if your data appears in other breaches.

  • Data: The exact data fields compromised in the Verified.cash 2019 breach are still under review. Updates will be published when confirmed.
  • Imported:
  • Number of lines: 1,128,617
  • Size: 325.4 MB
  • Passwords: MyBB
  • Cracked: 0%

At present, no extended description exists for the Ogonek.us 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.

  • Data: It is unclear which categories of data were compromised in the Ogonek.us 2011 breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 41,522
  • Size: 7.64 MB
  • Passwords: ?
In May 2020, the Nigerian Store website Konga.com suffered a data breach leading to almost 450,000 users emails, names, geographical locations and purchase logs to be leaked. The data was public facing due to poor website security.
  • Date: May 2020
  • Domain: konga.com
  • Country: Nicaragua
  • Category: E-commerce & Retail
  • Records Announced: 442,534
  • Data: Email Addresses Financial Information Geographic Locations Names Order Information
  • Imported:
  • Passwords: No
In February 2014, ZoXXe.eu, a German-based platform offering free voice and game servers for various games, experienced a data breach that exposed approximately 65,356 user records. The leaked data included usernames, email addresses, IP addresses and passwords.
  • Date: Feb 2014
  • Domain: zoxxe.eu
  • Category: Forums & Communities
  • Records Announced: 65,356
  • Source: hashmob.net
  • Data: Email Addresses Passwords Names IP Addresses
  • Imported:
  • Passwords: Unknown

We currently have no detailed description for the Lih.bz 2016 data breach. This page is part of our effort to track security incidents. You will be able to check your information against this breach once it has been processed. Until then, try our search tool for other breaches.

  • Date: 2016
  • Domain: lih.bz
  • Country: Belize
  • Data: The types of personal information exposed in the Lih.bz 2016 breach are not yet confirmed. This entry will be updated once verified sources provide details.
  • Imported:
  • Number of lines: 239,790
  • Size: 119.46 MB
  • Passwords: ?

Details about the Phreaker.us 2012 breach remain unavailable. Once it is imported, you will be able to check if your data was affected. Until then, you may search through other breaches to stay informed.

  • Data: At this stage, the exact nature of the compromised information in the Phreaker.us 2012 breach is unknown. Updates will be provided as they are verified.
  • Imported:
  • Number of lines: 5,033,561
  • Size: 438.5 MB
  • Passwords: ?

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.