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

Horizon Actuarial — November 2021 breach

Clustered 42 filings across 13 jurisdictions · filing window Mar 9, 2022 → Jun 13, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

42 filings

States

13

Affected · reported

2,302,441

First → last filing

Mar 9, 2022 → Jun 13, 2022

Merge confidence

100%

incident inc_a938a3534cbb4649 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 42 regulatory filings. Intrusion Nov 10, 2021–Nov 17, 2021, discovered Nov 12, 2021 — the first regulatory filing landed 117 days later (flagged late). 2,302,441 individuals reported across the linked filings. Data reported: Government ID, PHI, PII, and 6 more. Notifications rolled out on a 96-day schedule across 42 filings beginning Mar 9, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
117days

Discovered → first regulatory filing

Discovery variance
77days

Range of discovered_at dates across filings

Filing span
96days

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 clocksCalifornia✗ CA 60-day late · 62dMaine✗ ME AG >90d · 92dWashington✗ WA AG >90dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Nov 10, 2021breach begins
Nov 12, 2021discovered · members disagree
notification delay · 117 days
Mar 9, 2022first filing
Jun 13, 2022most 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 9HHS OCRHHS OCR noticefirst filing · states nationwide total 227,953day 0
  2. MAR 9CA AGCA AG noticeno count statedday 0
  3. MAR 9ME AGME AG noticestates nationwide total 13,198day 0
  4. MAR 22CA AGCA AG noticeno count stated+13d
  5. MAR 22IN AGIN AG noticestates nationwide total 194,195+13d
  6. MAR 22ME AGME AG noticestates nationwide total 42,384+13d
  7. MAR 22ME AGME AG noticestates nationwide total 6,323+13d
  8. MAR 22OR AGOR AG noticestates nationwide total 194,195+13d
  9. MAR 22WA AGWA AG notice53,256 WA residents+13d
  10. MAR 22ID AGID AG notice7 ID residents+13d
  11. MAR 22ME AGME AG noticestates nationwide total 13,156+13d
  12. MAR 22ME AGME AG noticestates nationwide total 194,195+13d
  13. MAR 22MT AGMT AG notice19,245 MT residents+13d
  14. MAR 22MA AGMA AG notice37,986 MA residents+13d
  15. MAR 23SC AGSC AG notice10,270 SC residents+14d
  16. MAR 24NH AGNH AG notice6 NH residents+15d
  17. MAR 25CA AGCA AG noticeno count stated+16d
  18. MAR 25ID AGID AG notice6,413 ID residents+16d
  19. MAR 28NH AGNH AG notice39 NH residents+19d
  20. MAR 29NH AGNH AG notice67 NH residents+20d
  21. APR 11ME AGME AG noticestates nationwide total 786,012+33d
  22. APR 11ID AGID AG notice6,645 ID residents+33d
  23. APR 11CA AGCA AG noticeno count stated+33d
  24. APR 11DE AGDE AG noticeno count stated+33d
  25. APR 15ME AGME AG noticestates nationwide total 1,309,870+37d
  26. APR 15CA AGCA AG noticeno count stated+37d
  27. APR 15NH AGNH AG notice1,071 NH residents+37d
  28. APR 18NH AGNH AG notice240 NH residents+40d
  29. APR 18CA AGCA AG noticeno count stated+40d
  30. APR 22NH AGNH AG notice1,746 NH residents+44d
  31. APR 26ME AGME AG noticestates nationwide total 1,312,212+48d
  32. MAY 10CA AGCA AG noticeno count stated+62d
  33. MAY 10ME AGME AG noticestates nationwide total 1,548,060+62d
  34. MAY 17NH AGNH AG notice1,806 NH residents+69d
  35. MAY 18CA AGCA AG noticeno count stated+70d
  36. MAY 24CA AGCA AG noticeno count stated+76d
  37. MAY 24HI AGHI AG notice5,793 HI residents+76d
  38. MAY 24ME AGME AG noticestates nationwide total 2,302,441+76d
  39. MAY 31NH AGNH AG notice2,926 NH residents+83d
  40. JUN 9ME AGME AG noticestates nationwide total 2,292,080+92d
  41. JUN 9CA AGCA AG noticeno count stated+92d
  42. JUN 13NH AGNH AG noticemost recent · 3,264 NH residents+96d
  43. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 10, 2021 – Nov 11, 2021
CA AG
Discovered
Nov 12, 2021CA AG + WA AG + ID AG +5Dec 29, 2021HHS OCR + ME AGJan 12, 2022ME AGJan 13, 2022ME AG + NH AGJan 28, 2022NH AGfilings disagree on discovery
Data types
Authentication · Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + NH AG + CA AG +8
Attack vector
Ransomware
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)

2,302,441

Sum of filed state slices

209,535· 9.1% of stated

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

US2,302,441
IN69,719
WA53,256
MA37,986
MT19,245
SC10,270
ID6,645
HI5,793
ME3,357
NH3,264

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 filing42 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 Aug 10, 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

96 days

Cadence

~1 / 2.3d

vs. multi-state median

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