Home All Breaches parapa.mail.ru_08.2016_5kk.7z

parapa.mail.ru_08.2016_5kk.7z

DBs w MTDT

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

Country
Discovered
2024-03-25
Breach ID
512e11ba494d

Breach Overview

📧 mail.ru 3mln On January 13, 2023, the NLB hacker group said that they managed to hack the Russian postal service Mail.ru.They claimed that they managed to steal 2 billion records, but they laid out only 3.5 million of them into public access.The leak contains mail, names and nicknames of users.Representatives of Mail.Ru said that hackers have no other records, except for published. 📩Email: 7,008,337 📞 Telephone: 3.524.062 👤fio: 3.277.939 👤nik: 2,333,013 | 155.06 MB | forwarded from: [Star Social].database

Dark Web Exposure

Cross-referenced against HaveIBeenRansom's dark-web index of ransomware leaks, breaches & infostealer logs.
0
found in Infostealer logs
0
found in Traditional breaches
0
found in Ransomware leaks
Emails exposed
••••
Internal
•••
External
•••
Distinct leaks
••
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
Full exposure is locked
See every breached email, the internal-vs-external split and each leak source behind this breach.
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this breach →
View Group: DBs w MTDT
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.