DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed12 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

CLEAR SPRING LIFE AND ANNUITY COMPANY — November 2022 breach

Clustered 12 filings across 9 jurisdictions · filing window Jul 27, 2023 → Nov 21, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

64,786

First → last filing

Jul 27, 2023 → Nov 21, 2023

Merge confidence

100%

incident inc_83f7d4f413ee43b1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe a ransomware attack. Intrusion Nov 30, 2022–Feb 9, 2023, discovered Feb 9, 2023 — the first regulatory filing landed 168 days later (flagged late). 64,786 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 117-day schedule across 12 filings beginning Jul 27, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
168days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
117days

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 · 168dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 169dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 30, 2022breach begins
Feb 9, 2023discovered
notification delay · 168 days
Jul 27, 2023first filing
Nov 21, 2023most 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. JUL 27ME AGME AG noticefirst filing · states nationwide total 4,393day 0
  2. JUL 28VT AGVT AG noticeno count stated+1d
  3. JUL 28WA AGWA AG notice1,125 WA residents+1d
  4. JUL 28MA AGMA AG notice1,292 MA residents+1d
  5. JUL 28OR AGOR AG noticestates nationwide total 63,045+1d
  6. JUL 28IN AGIN AG noticestates nationwide total 63,045+1d
  7. JUL 28CA AGCA AG noticeno count stated+1d
  8. JUL 28SC AGSC AG notice1,367 SC residents+1d
  9. AUG 1NH AGNH AG noticestates nationwide total 4,393+5d
  10. NOV 21CA AGCA AG noticeno count stated+117d
  11. NOV 21CA AGCA AG noticeno count stated+117d
  12. NOV 21OR AGOR AG noticemost recent · states nationwide total 64,786+117d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 9, 2023
ME AG
Discovered
Feb 9, 2023
ME AG + VT AG + WA AG +4
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + MA AG + VT AG +4
Attack vector
Ransomware
ME 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)

64,786

Sum of filed state slices

6,867· 10.6% of stated

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

US64,786
IN3,070
SC1,367
MA1,292
WA1,125
ME10
NH3

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

117 days

Cadence

~1 / 10.6d

vs. multi-state median

14.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.