This record tracks a ransomware attack claimed by the
medusa group against
The Professional Liability Fund . 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.
917days open
t1 · Published
t2 · Pending
Business Category
Communication / Marketing
Published
February 26, 2024
Disclosed / Notified
Not disclosed yet
Attack Summary
The Professional Liability Fund (PLC) was established in 1977 in accordance with state law (ORS 9.080) and with the approval of OSB members. PLF began its operations on July 1, 1978 and since that date has been a mandatory provider of primary negligence insurance for lawyers (more than 7,000 people) in the state of Oregon, the only U.S. state in which such insurance is mandatory. Professional Liability Fund corporate office is located in 16037 SW Upper Boones Ferry Rd Ste 300, Portland, Oregon, 97224, United States and has 68 employees.
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 osbplf.org
— indexed by HaveIBeenRansom.
0
found in Infostealer logs
564+
found in Traditional breaches
40+
found in Ransomware leaks
limeleads_breach.7z
TheUnderground - Reborn · breach
••• emails
VerificationsIO_BF.7z.011
Kedr | Forum · breach
••• emails
pureincubation-com.7z.001
Database World ROC · breach
••• emails
Carney Badley Spellman
play · ransomware
••• emails
Apollo.io DB 816millions.rar
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.