Breach Intelligence

2,850

Total breached databases

The Twycrosszoo.org 2018 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 Twycrosszoo.org 2018 security incident has not been specified. We are monitoring for reliable updates and will publish them here.
  • Imported:
  • Number of lines: 2,067
  • Size: 2.78 MB
  • Passwords: ?

At present, no extended description exists for the Thehackersbay.org 2014 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 Thehackersbay.org 2014 breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 61,305
  • Size: 24.68 MB
  • Passwords: MyBB
  • Cracked: 0%

The Bolseo.ru 2018 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 Bolseo.ru 2018 security incident has not been specified. We are monitoring for reliable updates and will publish them here.
  • Imported:
  • Number of lines: 129
  • Size: 16.77 KB
  • Passwords: ?
In approximately July 2012, the vBulletin forum for the Runescape private server, SilabGarza (Aka SG-Forum.info), suffered a data breach. The breached data included over 105k emails along with usernames, IP addresses, and passwords stored as salted MD5 hashes.
  • Date: Jul 2012
  • Domain: silabgarza.net
  • Category: Gaming
  • Records Announced: 105,360
  • Data: Email Addresses IP Addresses Passwords Usernames
  • Imported:
  • Number of lines: 105,365
  • Size: 11.35 MB
  • Passwords: MD5 Salted
  • Cracked: 0%
In August 2022, DoorDash, a food ordering and delivery service, disclosed a data breach that it attributed to a phishing attack on an unnamed third-party vendor. The incident reportedly impacted 367,000 customers. Among the compromised data were email addresses, names, postal codes, and partial payment card details, including the brand, expiry date, and last four digits.
  • Data: Credit Card Information Email Addresses Geographic Locations Names
  • Imported:
  • Passwords: No
In July 2023, Perception Point reported a phishing operation known as "Manipulated Caiman". The campaign primarily targeted citizens of Mexico and sought to gain access to victims' bank accounts through spear phishing attacks that utilized malicious attachments. Researchers uncovered nearly 40 million email addresses targeted in the campaign.
  • Date: Jul 16, 2023
  • Country: Mexico
  • Category: Hacking
  • Records Announced: 39,901,389
  • Source: haveibeenpwned.com
  • Data: Email Addresses
  • Imported:
  • Passwords: No

We do not yet have a full description for the Booter.tw 2013 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.

  • Date: 2013
  • Domain: booter.tw
  • Country: Taiwan
  • Category: Hacking
  • Records Announced: 314
  • Data: It is not yet known which data types were exposed in the Booter.tw 2013 incident. This page will be updated as more details are verified.
  • Imported:
  • Number of lines: 106,239
  • Size: 10.41 MB
  • Passwords: SHA-256
  • 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.