This record tracks a ransomware attack claimed by the
arcusmedia group against
PK Mulyo. 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.
653days open
t1 · Published
t2 · Pending
Published
November 20, 2024
Disclosed / Notified
Not disclosed yet
Attack Summary
Days06Hours23Minutes22223333Seconds11115555
www.mulyo.comThe Mulyo story began in Salatiga, Central Java, Indonesia, in 1965. At the t…
Leak Screenshots
2 CAPTURED
Captured directly from the operator's leak site by our collector.
Proof files published by the operator —
1 image(s) harvested from this entry.
Content is locked; type and dimensions shown.
Showing the latest capture only
Unlock the daily capture history — up to 45 days of evidence, plus the 1 proof file(s) the operator published.
Dark Web Exposure
Findings for mulyo.com
— indexed by HaveIBeenRansom.
46
found in Infostealer logs
11
found in Traditional breaches
0
found in Ransomware leaks
Exploit.in.rar
LKnet reserve chat · breach
••• emails
Wattpad_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
@BreachedData1 LinkedIn 2021-23 Cleaned.7z.001
Database World ROC · breach
••• emails
Dropbox_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
Tokopedia_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
B F R e p o V 3 F i l e s · breach
••• emails
Database World ROC · breach
••• emails
+ 2 more leak sources locked
Leak volumes are locked
Sign in to reveal how many records each source exposed and the remaining 5 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.
