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

North Los Angeles County Regional Center — November 2024 breach

Clustered 4 filings across 4 jurisdictions · filing window Jun 1, 2026 → Jul 6, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

5

First → last filing

Jun 1, 2026 → Jul 6, 2026

Merge confidence

100%

incident inc_adcdcc9733b14c8c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a ransomware attack. Intrusion Nov 20, 2024–Dec 1, 2024, discovered Nov 28, 2024 — the first regulatory filing landed 550 days later (flagged late). 5 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PII, and 2 more. Notifications rolled out on a 35-day schedule across 4 filings beginning Jun 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
550days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
35days

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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 20, 2024breach begins
Nov 28, 2024discovered
notification delay · 550 days
Jun 1, 2026first filing
Jul 6, 2026most 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 30NE AGNE AG noticeno count stated+29d
  3. JUN 30VT AGVT AG notice3 VT residents+29d
  4. JUL 6NH AGNH AG noticemost recent · 2 NH residents+35d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 20, 2024 – Dec 1, 2024
NE AG
Discovered
Nov 28, 2024· 8d undetected
IL AG + NE AG + NH AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + VT AG + NH AG +1
Attack vector
Ransomware
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

35 days

Cadence

~1 / 11.7d

vs. multi-state median

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