Medical Associates of Brevard, LLC
bd_f99356991afe3af4 · schema v1 · pii pii-v1
Full breach record for Medical Associates of Brevard, LLC →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group BianLian on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Medical Associates of Brevard (MAB) was first founded in 1996 to provide area residents with a central resource where they could find a highly skilled medical specialist to address virtually any health care needs they may require.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 17, 2025
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Maine State AGbd_00621575f72b9ba62025-09-05 · +231dVerified by operator
- Montana State AGbd_931740a61e3ad4362025-09-05 · +231dVerified by operator
- HHS OCRbd_e893a194966d9bcd2025-09-05 · +231dVerified by operator
- Indiana State AGbd_edb62dd27b0c7f3f2025-09-05 · +231dVerified by operator
Show 3 more filings ↓Show fewer ↑up to 266d gap
- Nebraska State AGbd_f5b2ee2c40dbf9572025-09-05 · +231dVerified by operator
- New Hampshire State AGbd_1a02292581ce4e212025-09-09 · +235dVerified by operator
- Maine State AGbd_336386adde25a7cf2025-10-10 · +266dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Sep 5 (ME), last Oct 10 (ME) — a 35-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
bianlian
According to ransomware.live, BianLian ransomware operations began in late 2021. The group practices multi-pronged extortion, demanding payment for a decryptor, as well as the non-release of stolen data. The ransomware group hosts a public, TOR-based, blog to post victim identities and stolen data. Somewhat unique to BianLian at the time of their launch was their inclusion of an I2P mirror for their blog.