DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed15 filings · 13 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 15 filings

Medusind, Inc. — December 2023 breach

Clustered 15 filings across 13 jurisdictions · filing window Jan 1, 2025 → Feb 20, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

15 filings

States

13

Affected · reported

701,475

First → last filing

Jan 1, 2025 → Feb 20, 2025

Merge confidence

100%

incident inc_7258bc348b3d4d7e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion Dec 29, 2023–Jan 7, 2024, discovered Dec 29, 2023 — the first regulatory filing landed 369 days later (flagged late). 701,475 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 50-day schedule across 15 filings beginning Jan 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
369days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
50days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 375dWashington✗ WA AG >90dOregon✗ OR AG >45dRhode Island✗ RI AG >45dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 29, 2023breach begins
Dec 29, 2023discovered
notification delay · 369 days
Jan 1, 2025first filing
Feb 20, 2025most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 7DE AGDE AG noticeno count stated+6d
  3. JAN 7NE AGNE AG noticeno count stated+6d
  4. JAN 7CA AGCA AG noticeno count stated+6d
  5. JAN 7IN AGIN AG noticestates nationwide total 319,965+6d
  6. JAN 7OR AGOR AG noticestates nationwide total 360,934+6d
  7. JAN 7HHS OCRHHS OCR noticestates nationwide total 701,475+6d
  8. JAN 7ME AGME AG noticestates nationwide total 360,934+6d
  9. JAN 8SC AGSC AG notice24,725 SC residents+7d
  10. JAN 8MA AGMA AG notice1,209 MA residents+7d
  11. FEB 11WA AGWA AG notice511 WA residents+41d
  12. FEB 11CA AGCA AG noticeno count stated+41d
  13. FEB 11OR AGOR AG noticestates nationwide total 691,192+41d
  14. FEB 18NH AGNH AG noticestates nationwide total 691,192+48d
  15. FEB 20RI AGRI AG noticemost recent · 81 RI residents+50d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 29, 2023
DE AG
Discovered
Dec 29, 2023
IL AG + DE AG + NE AG +6
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
DE AG + NE AG + CA AG +6
Attack vector
Unauthorized Access
NE AG

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)

701,475

Sum of filed state slices

31,467· 4.5% of stated

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

US701,475
SC24,725
IN2,241
NH1,677
MA1,209
ME1,023
WA511
RI81

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 report

No press coverage linked yet.

State AG / regulator filing15 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

50 days

Cadence

~1 / 3.6d

vs. multi-state median

6.3× 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.