Home › All Breaches › beboss.ru.csv

beboss.ru.csv

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
Russian Federation
Discovered
2025-04-05
Breach ID
da0e3609775a

Breach Overview

The data breach involving beboss.ru.csv was disclosed by the Misha-z88 DB threat actor. The exposed records are associated with Russian Federation. Breach House indexed this entry on April 05, 2025 from publicly posted breach listings. Breach House does not host, mirror or redistribute any leaked files — this record only notes that the listing was made public.

Dark Web Exposure

Findings for beboss.ru — indexed by HaveIBeenRansom.
61
found in Infostealer logs
85+
found in Traditional breaches
1+
found in Ransomware leaks
CDEK_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
cdek_2.zip.001
⚡️𝙎𝙏𝙊𝙍𝙈 Чат | База Данных · breach
••• emails
Exploit.in.rar
LKnet reserve chat · breach
••• emails
eda.yandex.ru CSV.zip
Misha-z88 DB · breach
••• emails
AntiPublic_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
DBs Backup · breach
••• emails
⚡️𝙎𝙏𝙊𝙍𝙈 Dаtа Ваsе · breach
••• emails
Durov · breach
••• 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.