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.
Clustered 2 filings across 2 jurisdictions · filing window Feb 2, 2025 → Sep 5, 2025. View entity profile → Other incidents for this victim →
incident inc_27561e73ae2f4309 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
PHI · PII
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 17, 2025
When the intrusion reportedly occurred, per the linked filings
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.
Jul 7, 2025
Reported by MAINE AG filing
Medical Associates of Brevard, LLC, a Florida-based healthcare provider, experienced a criminal cyberattack on January 17, 2025 that compromised protected health information (PHI) and personally identifiable information (PII). The breach was discovered on July 7, 2025, and 107 Maine residents were affected. The organization engaged third-party experts, secured its systems, and notified affected individuals on September 5, 2025. Experian identity protection services were offered.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 107