Home › All Breaches › discord.com (2).txt

discord.com (2).txt

Misha-z88 DB

This page documents a data breach listing tracked by Breach House. It summarizes the publicly advertised leak attributed to Misha-z88 DB, including the affected entity, origin and the date the listing was first indexed.

Country
Discovered
2025-05-08
Breach ID
b3534ebd034a

Breach Overview

The data breach involving discord.com (2).txt was disclosed by the Misha-z88 DB threat actor. Breach House indexed this entry on May 08, 2025 from publicly posted breach listings. No underlying stolen content is hosted or distributed here; this page documents only the publicly advertised existence of the leak.

Dark Web Exposure

Findings for discord.com — indexed by HaveIBeenRansom.
6,062,445
found in Infostealer logs
365+
found in Traditional breaches
30+
found in Ransomware leaks
pureincubation-com.7z.001
Database World ROC · breach
••• emails
linkedIN_2.7z.001
Database World ROC · breach
••• emails
contacts_120.csv
Database World ROC · breach
••• emails
combined_master.part01.rar
DL| Database catalog · breach
••• emails
@TXTLOG_ALIEN — @TXTLOG_LINK - 491.txt
Database World ROC · breach
••• emails
Database World ROC · breach
••• emails
Pma Dump · breach
••• emails
shinyhunters · ransomware
••• emails
+ 17 more leak sources locked
Leak volumes are locked
Sign in to reveal how many records each source exposed and the remaining 20 sources.
Sign in Unlock with Enterprise →
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this breach →
Original Post View Group: Misha-z88 DB

Related entries

@misha_z88db ULP (ROWS) 15000000Lines (1).txt @misha_z88db ULP (ROWS) 15000000Lines (2).txt @misha_z88db ULP (ROWS) 15000000Lines (3).txt @misha_z88db ULP (ROWS) 15000000Lines (4).txt @misha_z88db ULP (ROWS) 15000000Lines (5).txt @misha_z88db ULP (ROWS) 15000000Lines (6).txt
Legal Disclaimer: This breach record is compiled from publicly advertised leak listings. Breach.house only records what the operators themselves publish in the open. We take screenshots of their public pages and keep the proof material they post there, so that a listing can be verified and its status tracked over time. We do not purchase data, we do not solicit or encourage its publication, we do not access any private system, and we do not alter anything we record. Nothing is offered for download here, and detailed content is not published on this page or anywhere else on the public site: access to it is restricted to vetted customers under contract, for incident response, due diligence and cyber-resilience work. Breach.house is not affiliated with, and does not act on behalf of, the operators who publish this material. If you represent an organisation or individual named here and want a record reviewed or removed, contact us and we will act on it.