Breach Intelligence

2,848

Total breached databases

At this time, no official description is available for the Dress.ph 2019 incident. This record remains published to ensure transparency. Once imported, you will be able to check if your data was involved. For now, you can review other breaches to see if your information appears there.

  • Date: 2019
  • Domain: dress.ph
  • Country: Philippines
  • Data: At present, the information about what data was leaked in the Dress.ph 2019 breach remains unavailable. Further updates will follow.
  • Imported:
  • Number of lines: 266,378
  • Size: 129.71 MB
  • Passwords: ?
In late 2013, Crack Community, a forum focused on game cracks, allegedly suffered a data breach in which more than 19,000 accounts were published online. The MyBB-based forum reportedly exposed email addresses, IP addresses, and passwords stored as salted MD5 hashes.
  • Data: Email Addresses IP Addresses Passwords Site Activity Usernames
  • Imported:
  • Number of lines: 422,465
  • Size: 160.72 MB
  • Passwords: MD5 Salted
  • Cracked: 57%

The Ewhore.pro 2012 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.

  • Date: 2012
  • Domain: ewhore.pro
  • Category: Pornography
  • Records Announced: 794
  • Data: The data involved in the Ewhore.pro 2012 security incident has not been specified. We are monitoring for reliable updates and will publish them here.
  • Imported:
  • Number of lines: 72,259
  • Size: 21.35 MB
  • Passwords: MyBB
  • Cracked: 0%
In May 2022, Mangatoon, a Hong Kong-based manga service, allegedly suffered a data breach that exposed 23 million subscriber records. Among the compromised information were names, email addresses, genders, social media account identities, authentication tokens from social logins, and passwords stored as salted MD5 hashes.
  • Data: Email Addresses Genders Names Passwords Profile Photos Security Credentials Social Profiles Usernames
  • Imported:
  • Passwords: MD5 Salted
  • Cracked: 0%
In 2021, Alshaya Group, a leading brand franchise operator, experienced a data breach. The breach reportedly affected approximately 280,000 records. Among the compromised data were customer names, email addresses, phone numbers, geographic locations, and dates of birth.
  • Date: 2021
  • Domain: alshaya.com
  • Threat Actor: Chucky
  • Country: United Arab Emirates
  • Category: E-commerce & Retail
  • Records Announced: 281,068
  • Data: Email Addresses Names Phone Numbers Physical Locations Geographic Locations Birthdates
  • Imported:
  • Passwords: No

There is no official description for the Hesus-store.com 2019 data breach at this time. However, this record will allow future verification once the breach is processed. For now, you can use our search tool to see if your personal information appears in other breaches.

  • Data: The specific records exposed in the Hesus-store.com 2019 breach have not yet been identified. We will update this section with details when they are confirmed.
  • Imported:
  • Number of lines: 324,905
  • Size: 229.05 MB
  • Passwords: ?

We do not yet have a full description for the Bcwars.com 2011 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 Bcwars.com 2011 incident. This page will be updated as more details are verified.
  • Imported:
  • Number of lines: 101,779
  • Size: 5.67 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.