DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
PressHHS OCRSEC 8-KState AGConfirmed10 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

CareCloud, Inc. — March 2026 breach

Clustered 10 filings across 9 jurisdictions · filing window Mar 27, 2026 → Aug 6, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

3,371,508

First → last filing

Mar 27, 2026 → Aug 6, 2026

Merge confidence

100%

incident inc_1d29a297fc444c08 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 press report. The filings describe unauthorized access. Intrusion Mar 10, 2026–Jun 24, 2026, discovered Mar 16, 2026 — the first regulatory filing landed 11 days later (flagged late). 3,371,508 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 143-day schedule across 9 filings beginning Mar 27, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
11days

Discovered → first regulatory filing

Discovery variance
100days

Range of discovered_at dates across filings

Materiality delta
8days

Discovery to SEC materiality determination

SEC filing delay
3days

Materiality determination to SEC 8-K filing

Filing span
143days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksWashington✗ WA AG >90dMassachusetts✗ MA AG >90dOregon✗ OR AG >45dSEC✓ SEC 4-day OK · 3dHIPAA✓ HHS notifiedTexas✓ TX CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 10, 2026breach begins
Mar 16, 2026discovered · members disagree
notification delay · 11 days
Mar 27, 2026first filing
Aug 6, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 27SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 24HHS OCRHHS OCR noticestates nationwide total 3,371,508+119d
  3. JUL 24WA AGWA AG notice20,706 WA residents+119d
  4. JUL 25CA AGCA AG noticeno count stated+120d
  5. JUL 25MA AGMA AG notice72,102 MA residents+120d
  6. JUL 28TX AGTX AG noticestates nationwide total 3,371,508+123d
  7. JUL 31NH AGNH AG notice68,886 NH residents+126d
  8. AUG 4OR AGOR AG noticestates nationwide total 57,920+130d
  9. AUG 6SC AGSC AG noticemost recent · 24,153 SC residents+132d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 16, 2026
SEC 8-K
Discovered
Mar 16, 2026SEC 8-K + WA AG + CA AG +4Jun 24, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
SEC 8-K + HHS OCR + WA AG +5
Attack vector
Unauthorized Access
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

3,371,508

Sum of filed state slices

456,044· 13.5% of stated

86% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US3,371,508
TX270,197
MA72,102
NH68,886
SC24,153
WA20,706

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

143 days

Cadence

~1 / 15.9d

vs. multi-state median

17.9× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.