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

LCPtracker — August 2024 breach

Clustered 11 filings across 9 jurisdictions · filing window Nov 1, 2024 → Jan 14, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

42,220

First → last filing

Nov 1, 2024 → Jan 14, 2025

Merge confidence

100%

incident inc_7f5833dd31974d28 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Aug 14, 2024–Aug 20, 2024, discovered Aug 14, 2024 — the first regulatory filing landed 79 days later (flagged late). 42,220 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 74-day schedule across 11 filings beginning Nov 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
79days

Discovered → first regulatory filing

Discovery variance
6days

Range of discovered_at dates across filings

Filing span
74days

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 clocksWashington✗ WA AG >90dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 94dCalifornia✗ CA 60-day late · 143dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Aug 14, 2024breach begins
Aug 14, 2024discovered · members disagree
notification delay · 79 days
Nov 1, 2024first filing
Jan 14, 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. NOV 1IL AGIL AG noticefirst filing · no count statedday 0
  2. NOV 22CA AGCA AG noticeno count stated+21d
  3. NOV 22NH AGNH AG noticeno count stated+21d
  4. NOV 22WA AGWA AG noticestates nationwide total 42,220+21d
  5. NOV 22MT AGMT AG notice55 MT residents+21d
  6. NOV 22VT AGVT AG noticeno count stated+21d
  7. NOV 22MA AGMA AG notice168 MA residents+21d
  8. NOV 22ME AGME AG noticestates nationwide total 40,963+21d
  9. NOV 22IN AGIN AG noticestates nationwide total 40,963+21d
  10. DEC 20CA AGCA AG noticeno count stated+49d
  11. JAN 14CA AGCA AG noticemost recent · no count stated+74d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 14, 2024 – Aug 20, 2024
CA AG
Discovered
Aug 14, 2024IL AGAug 20, 2024CA AG + NH AG + WA AG +3filings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Identity (basic) · Government ID · PII
CA AG + NH AG + WA AG +4
Attack vector
Unauthorized Access
CA 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)

42,220

Sum of filed state slices

5,783· 13.7% of stated

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

US42,220
WA5,343
IN201
MA168
MT55
ME16

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

74 days

Cadence

~1 / 7.4d

vs. multi-state median

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