GLOBALClaimed by PearFirst sighting
Posted to leak site Sep 25, 2025bd_fbca2f8d470dced2
Provides a complete range of management services to healthcare providers
Clustered 3 filings across 3 jurisdictions · filing window Sep 25, 2025 → Jun 30, 2026. View entity profile → Other incidents for this victim →
incident inc_3d4705cf36d84e39 · merge_method deterministic · 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.
GA TX
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Provides a complete range of management services to healthcare providers
May 28, 2026
Reported by TEXAS AG filing
MCBS, LLC reported to HHS on 2026-06-26 a Hacking/IT Incident affecting 1,261,464 individuals. Breached information located on Network Server. Business Associate present.
Affected (this filing): 1,261,464
MCBS LLC based in Augusta, Georgia, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-05-28 and reported on 2026-06-30. 13,302 Texas residents were affected. 1,241,154 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Medical Information;Health Insurance Information;Date of Birth. Consumers were notified via Notice by publication in print media;Posted at company website or special website;U.S. Mail.
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): 13,302