Cybersecurity report
LeakBase Admin Arrested, Forums Exposed & Exploits Run Wild.
BreachAware, March 30, 2026. LeakBase's reappearance at leakbase.bz three days after the seizure, the arrest of its administrator 'Chucky', a 33-year-old, in Taganrog, Russia, and the forum's reliance on the Russian bulletproof provider DDoS-Guard..
- Source type
- Cybersecurity report
- Published
- March 30, 2026
- Research grade
- T2
- Used in entries
- 1
Bibliographic record
- Publisher
- BreachAware
- Published
- March 30, 2026
- Source type
- Cybersecurity report
- Research grade
- Source grade T2
- Language
- English
- Official record
- Not an official publication
- What it supports
- LeakBase's reappearance at leakbase.bz three days after the seizure, the arrest of its administrator 'Chucky', a 33-year-old, in Taganrog, Russia, and the forum's reliance on the Russian bulletproof provider DDoS-Guard.
- Dataset id
- src_breachaware_leakbase_2026
Research notes
- Page date line reads '30 March 2026 BREACHAWARE HQ'; the visible headline is 'LeakBase Admin Arrested, Forums Exposed & Exploits Run Wild.' while the browser title is the shorter 'LeakBase Arrest, Forum Leaks & Critical Exploits Rise'. The on-page headline is recorded.
- The arrest detail is sourced by BreachAware to Russian media footage, not to a charging authority - treat the arrest as reported, not confirmed by a prosecutor.
- The item sits inside BreachAware's periodic breach-roundup post; the LeakBase material is under its 'Cyber Update' section.
How this source is used
Cited 1 time across 1 record type.
The role on each citation records what the source was relied on for. A primary source establishes the fact, a supporting source corroborates it, technical evidence describes the infrastructure, and a later outcome records what happened afterwards.
Sources were reviewed to a research cutoff of August 23, 2026. Addresses recorded after that date are not reflected here.
Cited by
Later activity
1 citation
Cited for activity recorded after the takedown.
-
LeakBase (leakbase.bz)Later outcome
Same service on replacement infrastructure, LeakBase seizure