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

LCS Financial Services — February 2023 breach

Clustered 17 filings across 11 jurisdictions · filing window Sep 22, 2023 → Oct 24, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

11

Affected · reported

194,197

First → last filing

Sep 22, 2023 → Oct 24, 2023

Merge confidence

100%

incident inc_b5d037fd0dab455d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. The filings describe unauthorized access. Intrusion Feb 24, 2023–Feb 25, 2023, discovered Feb 25, 2023 — the first regulatory filing landed 209 days later (flagged late). 194,197 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 32-day schedule across 17 filings beginning Sep 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
209days

Discovered → first regulatory filing

Discovery variance
179days

Range of discovered_at dates across filings

Filing span
32days

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 clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 209dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 24, 2023breach begins
Feb 25, 2023discovered · members disagree
notification delay · 209 days
Sep 22, 2023first filing
Oct 24, 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. SEP 22IN AGIN AG noticefirst filing · states nationwide total 194,197day 0
  2. SEP 22VT AGVT AG noticeno count statedday 0
  3. SEP 22WA AGWA AG notice1,823 WA residentsday 0
  4. SEP 22MT AGMT AG notice726 MT residentsday 0
  5. SEP 22CA AGCA AG noticeno count statedday 0
  6. SEP 22MA AGMA AG notice4,308 MA residentsday 0
  7. SEP 22OR AGOR AG noticestates nationwide total 96,574day 0
  8. OCT 5NH AGNH AG notice1,394 NH residents+13d
  9. OCT 5DE AGDE AG noticeno count stated+13d
  10. OCT 5VT AGVT AG noticeno count stated+13d
  11. OCT 5CA AGCA AG noticeno count stated+13d
  12. OCT 6SC AGSC AG notice1,713 SC residents+14d
  13. OCT 24DE AGDE AG noticeno count stated+32d
  14. OCT 24CA AGCA AG noticeno count stated+32d
  15. OCT 24VT AGVT AG noticeno count stated+32d
  16. OCT 24HHS OCRHHS OCR noticestates nationwide total 768+32d
  17. OCT 24NH AGNH AG noticemost recent · 1,430 NH residents+32d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 24, 2023
IN AG
Discovered
Feb 25, 2023VT AG + WA AG + MT AG +4Aug 23, 2023OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + WA AG + MT AG +6
Attack vector
Unauthorized Access
VT 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)

194,197

Sum of filed state slices

12,940· 6.7% of stated

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

US194,197
MA4,308
IN2,940
WA1,823
SC1,713
NH1,430
MT726

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

32 days

Cadence

~1 / 2d

vs. multi-state median

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