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.
Breach Overview
How to Setup? 📁 Create a new bot at @BotFather and copy Bot Token. Go to @chat_id_echo_bot and type bot and start it. Copy your Chat ID. Open gate.php (From Phemedrone Gate Floder) using any text editor and replace YOUR TELEGRAM BOT TOKEN with the bot token you copied before and replace YOUR CHAT ID with your copied Chat ID. Upload gate.php on any hosting service to a public html folder. Create "logs" (without quotes) folder in the same location as gate.php. Open the project in a C# IDE (for e.g. Visual Studio). Open Config.cs and change GateURL variable to your Gate URL (for e.g. http://yourhosting.com/gate.php). Config.cs also contains other variables that you may modify for better experience. Change build type to Release and then build the project. Output executable will be located at ./Phemedrone-Stealer/bin/Release folder. Here you go | 120.15 KB | forwarded from: Hunt3r Kill3rs | Охотники-убийцы
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
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
Full exposure is locked
See every breached email, the internal-vs-external split and each leak source behind this breach.
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.