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

Financial Business and Consumer Solutions — February 2024 breach

Clustered 42 filings across 11 jurisdictions · filing window Apr 4, 2024 → Nov 27, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

42 filings

States

11

Affected · reported

4,253,394

First → last filing

Apr 4, 2024 → Nov 27, 2024

Merge confidence

100%

incident inc_c0b3e97baa994677 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 42 regulatory filings. Intrusion Feb 14, 2024–Feb 26, 2024, discovered Feb 26, 2024 — the first regulatory filing landed 38 days later (flagged late). 4,253,394 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 237-day schedule across 42 filings beginning Apr 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
38days

Discovered → first regulatory filing

Discovery variance
142days

Range of discovered_at dates across filings

Filing span
237days

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 · 93dVermont✗ VT AG >45 bdayWashington⏱ WA AG >30dSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 14, 2024breach begins
Feb 26, 2024discovered · members disagree
notification delay · 38 days
Apr 4, 2024first filing
Nov 27, 2024most 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 4DE AGDE AG noticefirst filing · no count statedday 0
  2. APR 26CA AGCA AG noticeno count stated+22d
  3. APR 26NH AGNH AG notice4,793 NH residents+22d
  4. APR 26IN AGIN AG noticestates nationwide total 1,955,385+22d
  5. APR 26SC AGSC AG notice125,056 SC residents+22d
  6. APR 26MT AGMT AG notice7,735 MT residents+22d
  7. APR 26WA AGWA AG notice25,175 WA residents+22d
  8. APR 26ME AGME AG noticestates nationwide total 1,955,385+22d
  9. APR 26VT AGVT AG noticeno count stated+22d
  10. APR 26OR AGOR AG noticestates nationwide total 1,955,385+22d
  11. MAY 10NH AGNH AG noticeno count stated+36d
  12. MAY 10DE AGDE AG notice6,574 DE residents+36d
  13. MAY 10ME AGME AG noticestates nationwide total 2,679,555+36d
  14. MAY 10CA AGCA AG noticeno count stated+36d
  15. MAY 29CA AGCA AG noticeno count stated+55d
  16. MAY 29ME AGME AG noticestates nationwide total 3,226,631+55d
  17. MAY 29DE AGDE AG noticeno count stated+55d
  18. MAY 29NH AGNH AG noticeno count stated+55d
  19. JUN 4HHS OCRHHS OCR noticestates nationwide total 145,211+61d
  20. JUN 19DE AGDE AG noticeno count stated+76d
  21. JUN 20ME AGME AG noticestates nationwide total 3,435,640+77d
  22. JUN 20CA AGCA AG noticeno count stated+77d
  23. JUN 20NH AGNH AG noticeno count stated+77d
  24. JUL 8NH AGNH AG noticeno count stated+95d
  25. JUL 8ME AGME AG noticestates nationwide total 4,050,711+95d
  26. JUL 8CA AGCA AG noticeno count stated+95d
  27. JUL 10ME AGME AG noticestates nationwide total 4,077,016+97d
  28. JUL 10NH AGNH AG noticeno count stated+97d
  29. JUL 10CA AGCA AG noticeno count stated+97d
  30. JUL 17NH AGNH AG noticeno count stated+104d
  31. JUL 17CA AGCA AG noticeno count stated+104d
  32. JUL 17ME AGME AG noticestates nationwide total 4,171,097+104d
  33. JUL 19CA AGCA AG noticeno count stated+106d
  34. JUL 19NH AGNH AG noticeno count stated+106d
  35. JUL 19ME AGME AG noticestates nationwide total 4,233,971+106d
  36. JUL 23NH AGNH AG noticeno count stated+110d
  37. JUL 23ME AGME AG noticestates nationwide total 4,253,394+110d
  38. JUL 23CA AGCA AG noticeno count stated+110d
  39. SEP 26VT AGVT AG noticeno count stated+175d
  40. SEP 26ME AGME AG noticestates nationwide total 626,396+175d
  41. OCT 3ME AGME AG noticestates nationwide total 237,703+182d
  42. NOV 27CA AGCA AG noticemost recent · no count stated+237d
  43. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 14, 2024 – Feb 26, 2024
DE AG
Discovered
Feb 26, 2024DE AG + CA AG + NH AG +5Jul 16, 2024ME AGJul 17, 2024ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + CA AG + NH AG +6
Attack vector
Unauthorized Access
DE 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)

4,253,394

Sum of filed state slices

249,302· 5.9% of stated

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

US4,253,394
SC125,056
IN72,128
WA25,175
ME7,841
MT7,735
DE6,574
NH4,793

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

237 days

Cadence

~1 / 5.8d

vs. multi-state median

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