# Data Breach Database

The Data Breach Database in Menaxa is a comprehensive, real-time log of security breaches and exposed data leaks — giving teams complete visibility into who was breached, when, what was stolen, and how severe it was.

Whether you’re tracking risk, monitoring brand mentions, or researching attack patterns, this database lets you search, filter, and investigate breaches with precision.

<figure><img src="https://1033706607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0czXBYc9NwxtN09GwZgK%2Fuploads%2FfIntJCw4DLkaOu1GzNWh%2Fscreencapture-localhost-3000-data-leaks-2025-05-12-17_19_19.png?alt=media&#x26;token=89fc0b2c-6a2f-42c4-bcc1-19bd658075d8" alt=""><figcaption></figcaption></figure>

***

## 📦 What It Tracks

| Metric          | Description                                        |
| --------------- | -------------------------------------------------- |
| Total Breaches  | Count of tracked security incidents across the web |
| Exposed Records | Total number of leaked/compromised data points     |
| Major Breaches  | Incidents with over 1 million records affected     |

***

## 🔎 Database Table Overview

| Column      | Description                                                           |
| ----------- | --------------------------------------------------------------------- |
| Breach Name | Organization or domain that was compromised                           |
| Breach Date | The confirmed or reported date of the incident                        |
| Data Types  | Types of data exposed: emails, passwords, IPs, card numbers, and more |
| Records     | Count of affected data points (e.g., 1,000,000 email-password pairs)  |

Each breach name is clickable and leads to a detailed view (coming soon), which includes:

* > Description of how the breach occurred
  >
  > Type of attack (if known)
  >
  > Sources (e.g. Telegram dump, dark web, public repo)
  >
  > Mitigation or response actions (if reported)

***

### 📊 Filter Options

* Search by breach name, organization, domain, or dataset
* Filter by:
  * Data Type (e.g., passwords, phone numbers, card details)
  * Date Range
  * Record Count
  * Severity (Major breaches over 1M)\\

Use these tools to:

* Monitor sensitive domains
* Track leaked customer data types
* Cross-reference threat activity with your tech stack or customers

***

## 🧠 Use Cases by Role

| Role           | Value                                                            |
| -------------- | ---------------------------------------------------------------- |
| Security teams | Track attack surfaces, notify stakeholders of exposure risks     |
| Product teams  | Monitor data leaks involving your brand, suppliers, or customers |
| Researchers    | Study attack frequency, source behavior, and data type evolution |
| CTOs/Leaders   | Understand breach impact on business trust and compliance        |

***
