This record tracks a ransomware attack claimed by the
Eclipse group against
dipecarr.com.br. 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.
1day open
t1 · Published
t2 · Pending
Indexed by Breach House
October 08, 2026
Disclosed / Notified
Not disclosed yet
Attack Summary
[AI generated] N/A
I don't have reliable, verifiable information about a company operating at "dipecarr.com.br." I'm unable to confirm its business activities, industry classification, or operational details with confidence. Providing fabricated details about an unfamiliar domain could result in inaccurate threat intelligence. If you have additional context or source material about this entity, I'd be glad to help analyze it.
Leak Screenshots
1 CAPTURED
Captured directly from the operator's leak site by our collector. Verdict evidence: listed on the leak site; no evidence of publication yet
Capture history —
2 day(s) tracked. Content is locked.
Showing the latest capture only
Unlock the 2 captures already taken.
Dark Web Exposure
Findings for dipecarr.com.br
— indexed by HaveIBeenRansom.
2
found in Infostealer logs
263+
found in Traditional breaches
29+
found in Ransomware leaks
15000000.txt
DBs Backup · breach
••• emails
ValeCard
medusa · ransomware
••• emails
Hotel Urbano (1).rar
DBs w MTDT · breach
••• emails
148GB (43).txt
DBs Backup · breach
••• emails
Log_Pass_4.txt
DBs Backup · breach
••• emails
Anonymous Russia БД · 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.
