MCBS, LLC
bd_fbca2f8d470dced2 · schema v1 · pii pii-v1
Full breach record for MCBS, LLC →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Pear 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
Provides a complete range of management services to healthcare providers
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 25, 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 (6) · sorted by filing gap
- California State AGbd_32aaf81428502adc2026-06-26 · +274dVerified by operator
- HHS OCRbd_8ed31a4b32add53a2026-06-26 · +274dVerified by operator
- New Hampshire State AGbd_8f3ea50c0a24e40c2026-06-29 · +277dVerified by operator
- Texas State AGbd_51bebdfc54a78a9b2026-06-30 · +278dVerified
Show 2 more filings ↓Show fewer ↑up to 279d gap
- South Carolina State AGbd_bf3c11705b24a8a62026-07-01 · +279dVerified
- Illinois State AGbd_bf98d272641890612026-07-01 · +279dVerified
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing Jun 26 (CA), last Jul 1 (IL) — a 5-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.
pear
According to ransomware.live, Pure Extraction And Ransom (PEAR) Team is the community of highly responsible and strictly disciplined members. We are a private team and have nothing common with any other threat actors. We've been monitoring this field for a long-long time. So, we understand all the processes and know well how it all works.