Breach Intelligence

2,850

Total breached databases

In January 2018, the Joomla template website JoomlArt inadvertently exposed more than 22k unique customer records in a Jira ticket. The exposed data was from iJoomla and JomSocial, both services that JoomlArt acquired the previous year. The data included usernames, email addresses, purchases and passwords stored as MD5 hashes. When contacted, JoomlArt advised they were aware of the incident and had previously notified impacted parties.
  • Data: Email Addresses Names Passwords Payment Information Usernames
  • Imported:
  • Passwords: MD5
  • Cracked: 0%

We do not yet have a full description for the Forum.bcss.org.uk 2023 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 Forum.bcss.org.uk 2023 incident. This page will be updated as more details are verified.
  • Imported:
  • Number of lines: 9,905,355
  • Size: 797.31 MB
  • Passwords: ?
In 2020, the website jmbullion.com, known for trading precious metals online, suffered a data breach. Reports suggest that the breach exposed approximately 490,000 customer records. Some of the leaked data includes email addresses and passwords hashed using PHPass.
  • Date: 2020
  • Domain: jmbullion.com
  • Country: United States
  • Category: E-commerce & Retail
  • Records Announced: 486,513
  • Source: hashmob.net
  • Data: Email Addresses Passwords
  • Imported:
  • Passwords: PHPass
  • Cracked: 0%
In August 2016, GeekedIn, a technology recruitment site, allegedly suffered a data breach after an exposed MongoDB database was accessed by an unknown third party. The breached dataset, originally scraped from GitHub in violation of its terms of use, contained over 8 million records. Among the compromised information were details from public profiles, including more than 1 million members’ email addresses.
  • Data: Email Addresses Geographic Locations Job Information Names Usernames
  • Imported:
  • Number of lines: 790,404,129
  • Size: 30.06 GB
  • Passwords: No

At present, no extended description exists for the Carder.pro 2013 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: 2013
  • Domain: carder.pro
  • Category: Hacking
  • Records Announced: 73,983
  • Data: It is unclear which categories of data were compromised in the Carder.pro 2013 breach. This page will be revised as information becomes available.
  • Imported:
  • Number of lines: 2,612,376
  • Size: 597.18 MB
  • Passwords: vBulletin
  • Cracked: 0%
In December 2022, the Biolinks website e.rip (Now defunct) suffered a data breach. The breach led to the exposure of data including Email addresses, Usernames, IP Addresses, Timezones, Social media profiles, User-agents and Passwords stored as bcrypt hashes. In total, 25.2k users were affected. The breach was acknowledged by staff in their discord and then they subsequently sold the domain.
  • Date: Dec 2022
  • Domain: e.rip
  • Category: Technology
  • Records Announced: 25,245
  • Data: Device Information Email Addresses IP Addresses Passwords Social Profiles Time Zones Usernames
  • Imported:
  • Number of lines: 3,124,247
  • Size: 486.49 MB
  • Passwords: BCrypt
  • Cracked: 0%

The Discus.solutions 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 Discus.solutions security incident has not been specified. We are monitoring for reliable updates and will publish them here.
  • Imported:
  • Number of lines: 2,886,047
  • Size: 2.04 GB
  • 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.