emailbomber.net
Dec 14, 2025
Database dump from EmailBomber v4, a paid email/SMS/call bombing (harassment/spam) service. The breach contains user accounts, subscription/payment records (cryptocurrency transactions including Bitcoin, ETH, USDT, Litecoin, Solana, XMR), license keys, ban lists, mass DM records, and daily operational statistics. Data spans from August 2024 through at least December 2025. The service accepted crypto payments and tracked approximately 119,839 users with 78,740 total bomb operations.
Data found in this dataset
Source files
Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.
emailbomberv4__banlist.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII present in sample rows. The file contains only two columns: 'id' (numeric internal identifier) and 'user_id' (numeric auto-generated identifier). Both are excluded per rules as internal IDs. No emails, names, addresses, or other PII fields are visible.
emailbomberv4__charges.csv1 column0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | user_id | high | column header 'user_id', values are numeric user identifiers |
Notes: The file contains transaction records for an email bombing service. The only PII present is numeric user IDs, which are considered internal identifiers and should be skipped per exclusion rules. All other columns contain transaction metadata, status flags, timestamps, and cryptocurrency types — none contain personal identifiers.
emailbomberv4__daily_stats.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only operational statistics and transactional data (counts of users, bombs, credits, amounts). No personal identifiable information (PII) fields are present. All columns represent aggregated metrics or financial/cryptocurrency transaction counts, which are excluded by the rules.
emailbomberv4__data.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only aggregate statistics (total_bombs, total_users, total_calls) with no personal identifying information. No PII fields are present.
emailbomberv4__keys.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a structured CSV file with four columns: id, key_value, duration, credits. None of the columns contain PII. The key_value column contains alphanumeric license keys, duration contains numeric time values, and credits contains numeric values. All columns are non-PII per the exclusion rules.
emailbomberv4__massdm.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal numeric IDs (user_id and id columns). No PII fields are present. The data appears to be internal account identifiers from the EmailBomber v4 service breach, with no email addresses, names, or other personal data exposed in these columns.
emailbomberv4__users.csv1 column69,746 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'username', values are unique alphanumeric strings suitable as login identifiers |
Notes: Only username column contains PII. All other columns are internal IDs, timestamps, counters, or license keys which are skipped per exclusion rules. No email, phone, name, address, DOB, SSN, password, or gender data present.