Breach Intelligence

2,850

Total breached databases

In May 2024, 2B rows of data with 361M unique email addresses were collated from malicious Telegram channels. The data contained 122GB across 1.7k files with email addresses, usernames, passwords and in many cases, the website they were entered into. The data appears to have been sourced from a combination of existing combolists and info stealer malware.
  • Date: May 28, 2024
  • Category: Compilations & Combo lists
  • Records Announced: 361,468,099
  • Source: haveibeenpwned.com
  • Data: Email Addresses Passwords Usernames
  • Imported:
  • Passwords: Unknown

Details about the Coders 2019 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.

  • Date: 2019
  • Domain: coders.to
  • Records Announced: 1,237
  • Data: At this stage, the exact nature of the compromised information in the Coders 2019 breach is unknown. Updates will be provided as they are verified.
  • Imported:
  • Passwords: ?

At present, no extended description exists for the Coinpaper.it 2019 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 Coinpaper.it 2019 breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 4,944,759
  • Size: 919.71 MB
  • Passwords: ?

There is no official description for the Scoobies.co.in 2021 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 Scoobies.co.in 2021 breach have not yet been identified. We will update this section with details when they are confirmed.
  • Imported:
  • Number of lines: 15,489
  • Size: 11.9 MB
  • Passwords: ?
The Colorado 2017 Voter Database, containing approximately 3.6 million records, was uploaded on a hacking forum. Compromised data includes Voter IDs, Full Names, Physical Addresses, Previous Addresses, Dates of Birth, Genders, Phone Numbers, and Voter Status. The breach does not include any passwords or email addresses.
More information on similar breaches can be found on RF Database Index.
  • Date: 2017
  • Domain: colorado.gov
  • Country: United States
  • Category: Government
  • Records Announced: 3,692,353
  • Data: Names Phone Numbers Physical Locations Government IDs Genders Birthdates Political Affiliation
  • Imported:
  • Passwords: No

We do not yet have a full description for the Forme.am 2022 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 Forme.am 2022 incident. This page will be updated as more details are verified.
  • Imported:
  • Number of lines: 8,880,880
  • Size: 9.68 GB
  • Passwords: ?
On September 25, 2019, Com2us, a gaming platform, experienced a data breach. The exposed information reportedly comprised 228,639 lines of data. Among the compromised data were email addresses, IP addresses, usernames, and BCrypt-hashed passwords.
  • Date: Sep 25, 2019
  • Domain: com2us.com
  • Category: Gaming
  • Records Announced: 228,639
  • Data: Email Addresses Passwords Usernames IP Addresses
  • Imported:
  • Passwords: BCrypt
  • 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.