DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed9 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 9 filings

Kronick Moskovitz Tiedemann & Girard — July 2024 breach

Clustered 9 filings across 5 jurisdictions · filing window Aug 6, 2024 → May 30, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

4

Affected · reported

8,162

First → last filing

Aug 6, 2024 → May 30, 2025

Merge confidence

100%

incident inc_e90c1d30baf44255 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jul 19, 2024, discovered Aug 1, 2024 — the first regulatory filing landed 179 days later (flagged late). 8,162 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 297-day schedule across 7 filings beginning Aug 6, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
179days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
174days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
297days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 239dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 19, 2024breach begins
Aug 1, 2024discovered
notification delay · 179 days
Jan 27, 2025first filing
May 30, 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. AUG 6Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. AUG 22Leak siterhysida postattacker claim · unverified+17d
  3. JAN 27MA AGMA AG notice33 MA residents+174d
  4. FEB 28HHS OCRHHS OCR noticestates nationwide total 2,511+206d
  5. FEB 28CA AGCA AG noticeno count stated+206d
  6. MAR 28CA AGCA AG noticeno count stated+234d
  7. MAR 28VT AGVT AG noticeno count stated+234d
  8. MAR 28IN AGIN AG noticestates nationwide total 8,162+234d
  9. MAY 30CA AGCA AG noticemost recent · no count stated+297d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 19, 2024
CA AG
Discovered
Aug 1, 2024· 13d undetected
CA AG + VT AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + CA AG + VT AG +1
Attack vector
Unauthorized Access
HHS OCR

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)

8,162

Sum of filed state slices

84· 1.0% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

297 days

Cadence

~1 / 37.1d

vs. multi-state median

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