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

KELLY & ASSOCIATES INSURANCE GROUP, INC. — December 2024 breach

Clustered 30 filings across 14 jurisdictions · filing window Apr 9, 2025 → Jul 1, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

30 filings

States

14

Affected · reported

553,660

First → last filing

Apr 9, 2025 → Jul 1, 2025

Merge confidence

100%

incident inc_e45b6d38d7f342c3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 30 regulatory filings. The filings describe unauthorized access. Intrusion Dec 12, 2024–Dec 17, 2024, discovered Dec 12, 2024 — the first regulatory filing landed 118 days later (flagged late). 553,660 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 3 more. Notifications rolled out on a 83-day schedule across 30 filings beginning Apr 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
118days

Discovered → first regulatory filing

Discovery variance
81days

Range of discovered_at dates across filings

Filing span
83days

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 · 119dOregon✗ OR AG >45dIowa✗ IA AG >5 bdayWashington✗ WA AG >90dTexas✗ TX AG >30dHIPAA✓ HHS report on timeMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 12, 2024breach begins
Dec 12, 2024discovered · members disagree
notification delay · 118 days
Apr 9, 2025first filing
Jul 1, 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. APR 9IN AGIN AG noticefirst filing · states nationwide total 32,234day 0
  2. APR 9HHS OCRHHS OCR noticestates nationwide total 553,332day 0
  3. APR 9NH AGNH AG notice15 NH residentsday 0
  4. APR 9MA AGMA AG notice6,544 MA residentsday 0
  5. APR 9ME AGME AG noticestates nationwide total 32,234day 0
  6. APR 9DE AGDE AG notice1,942 DE residentsday 0
  7. APR 9CA AGCA AG noticeno count statedday 0
  8. APR 10SC AGSC AG notice5,793 SC residents+1d
  9. APR 21OR AGOR AG noticestates nationwide total 263,893+12d
  10. APR 21IA AGIA AG notice1,192 IA residents+12d
  11. APR 21ME AGME AG noticestates nationwide total 263,893+12d
  12. APR 21WA AGWA AG notice5,640 WA residents+12d
  13. APR 21NH AGNH AG notice456 NH residents+12d
  14. APR 21CA AGCA AG noticeno count stated+12d
  15. MAY 2NH AGNH AG notice595 NH residents+23d
  16. MAY 2CA AGCA AG noticeno count stated+23d
  17. MAY 2ME AGME AG noticestates nationwide total 413,032+23d
  18. MAY 12RI AGRI AG notice489 RI residents+33d
  19. MAY 30NH AGNH AG notice941 NH residents+51d
  20. MAY 30MT AGMT AG notice1 MT residents+51d
  21. MAY 30CA AGCA AG noticeno count stated+51d
  22. MAY 30DE AGDE AG noticeno count stated+51d
  23. MAY 30ME AGME AG noticestates nationwide total 488,139+51d
  24. JUN 5RI AGRI AG notice672 RI residents+57d
  25. JUN 30MT AGMT AG notice420 MT residents+82d
  26. JUN 30NH AGNH AG notice1,026 NH residents+82d
  27. JUN 30ME AGME AG noticestates nationwide total 553,660+82d
  28. JUN 30DE AGDE AG noticeno count stated+82d
  29. JUN 30CA AGCA AG noticeno count stated+82d
  30. JUL 1TX AGTX AG noticemost recent · states nationwide total 553,660+83d
  31. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 12, 2024
IN AG
Discovered
Dec 12, 2024WA AG + RI AGDec 17, 2024SC AG + IA AG + NH AG +1Mar 3, 2025HHS OCR + ME AG + OR AG +1filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + TX AG +9
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)

553,660

Sum of filed state slices

64,606· 11.7% of stated

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

US553,660
ME18,855
TX17,775
MA6,544
SC5,793
WA5,640
IN4,747
DE1,942
IA1,192
NH1,026
RI672
MT420

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 filing30 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

83 days

Cadence

~1 / 2.9d

vs. multi-state median

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