This record tracks a ransomware attack claimed by the
blacksuit group against
gbhs.org 07/12 Publication 51gb. It collects the publicly disclosed attack details — sector, location and
timeline — as published on the operator's leak site and indexed by Breach House.
Window Zero
EXPOSURE GAP
Window Zero is the time the breach stayed in the open before
anyone said so — the gap between when the attack was first discovered
on the operator's leak site (t1) and when it was publicly disclosed (t2).
The wider this window, the longer victims, staff and customers were exposed with no warning.
802days open
t1 · Published
t2 · Pending
Business Category
Public Sector
Disclosed / Notified
Not disclosed yet
Attack Summary
gbhs.org 07/12 Publication 51gb was named by the blacksuit ransomware group as a targeted organization. It operates in the Public Sector sector. The attack was first observed on July 13, 2024 and published on the group's leak site on June 21, 2024. Breach House tracks this attack from public ransomware leak-site postings for threat-intelligence purposes.
Leak Screenshots
SAMPLE
Proof-of-breach screenshots the operator posted from the stolen data. Previews are
redacted and locked — the originals are available on HaveIBeenRansom.
Dark Web Exposure
Findings for gbhs.org
— indexed by HaveIBeenRansom.
0
found in Infostealer logs
349+
found in Traditional breaches
3+
found in Ransomware leaks
limeleads_breach.7z
TheUnderground - Reborn · breach
••• emails
VerificationsIO_BF.7z.011
Kedr | Forum · breach
••• emails
Apollo.io DB 816millions.rar
Database World ROC · breach
••• emails
pureincubation-com.7z.001
Database World ROC · breach
••• emails
@BreachedData1 LinkedIn 2021-23 Cleaned.7z.001
Database World ROC · breach
••• emails
Database World ROC · breach
••• emails
B F R e p o V 3 F i l e s · 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.
Legal Disclaimer:
This ransomware victim record reflects information published on the operator's leak site.
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.