DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvhigh sensitivity
Merged incident · 11 filings

DISH NETWORK CORPORATION — February 2022 breach

Clustered 11 filings across 11 jurisdictions · filing window Jan 1, 2023 → May 22, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

296,851

First → last filing

Jan 1, 2023 → May 22, 2023

Merge confidence

100%

incident inc_b841297e15944d6c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Feb 22, 2022–Feb 23, 2023, discovered Feb 23, 2023. 296,851 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 5 more. Notifications rolled out on a 141-day schedule across 11 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
74days

Range of discovered_at dates across filings

Filing span
141days

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.

Regulatory clocksWashington⏱ WA AG >30dMaine✓ ME AG ≤30d · 10dOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 22, 2022breach begins
Feb 23, 2023discovered · members disagree
Jan 1, 2023first filing
May 22, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 28SEC 8-KSEC 8-K noticeno count stated+58d
  3. MAY 15IN AGIN AG noticestates nationwide total 296,832+134d
  4. MAY 16MT AGMT AG notice181 MT residents+135d
  5. MAY 16NH AGNH AG notice500 NH residents+135d
  6. MAY 17MA AGMA AG notice1,429 MA residents+136d
  7. MAY 18CA AGCA AG noticeno count stated+137d
  8. MAY 18ME AGME AG noticestates nationwide total 296,851+137d
  9. MAY 18OR AGOR AG noticestates nationwide total 296,832+137d
  10. MAY 18WA AGWA AG notice3,391 WA residents+137d
  11. MAY 22SC AGSC AG noticemost recent · 8,449 SC residents+141d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 22, 2023
IN AG
Discovered
Feb 23, 2023IL AG + SEC 8-K + MT AG +2May 8, 2023ME AG + OR AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + NH AG + CA AG +4
Attack vector
Ransomware
SEC 8-K

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)

296,851

Sum of filed state slices

17,883· 6.0% of stated

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

US296,851
SC8,449
IN3,404
WA3,391
MA1,429
ME529
NH500
MT181

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 filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

141 days

Cadence

~1 / 14.1d

vs. multi-state median

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