Confirmed breach. Intrusion Jun 23, 2021–Oct 17, 2021, discovered Oct 17, 2021 — the first regulatory filing landed 165 days later. 2 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
2
Government ID · Identity (basic)
Jurisdictions
1
NH
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 23, 2021 → Oct 17, 2021
When the intrusion reportedly occurred, per the linked filings
Sinclair Broadcast Group notified the NH Attorney General of a ransomware incident. Unauthorized activity occurred between June 23 and October 17, 2021. The breach affected 2 New Hampshire residents, exposing names and Social Security numbers. Notification letters were mailed on March 31, 2022, offering one year of identity monitoring.
Affected (this filing): 2
Leak >90d
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.