Confirmed breach. Intrusion Nov 20, 2024–Dec 1, 2024, discovered Nov 28, 2024 — the first regulatory filing landed 579 days later (flagged late). 2 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2
Data types
—
Jurisdictions
2
NH VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 20, 2024 → Dec 1, 2024
When the intrusion reportedly occurred, per the linked filings
North Los Angeles County Regional Center reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-06-30. The reporting organization type is Health Care. 3 Vermont residents were affected. Categories of data breached: Social Security Numbers, Health Records.
Leak >180d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
North Los Angeles County Regional Center (NLACRC) notified the New Hampshire Attorney General of a ransomware incident. Unauthorized access occurred between November 20 and December 1, 2024. NLACRC discovered the activity on November 28, 2024. The attacker exfiltrated PII and PHI before encrypting systems. Two New Hampshire residents were affected. Notification to residents began June 30, 2026.
Affected (this filing): 2
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.