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

COMCAST CABLE COMMUNICATIONS, LLC — October 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Dec 18, 2023 → Jan 26, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

35,879,455

First → last filing

Dec 18, 2023 → Jan 26, 2024

Merge confidence

100%

incident inc_658e54a53e6c405e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Oct 16, 2023–Oct 19, 2023, discovered Oct 16, 2023 — the first regulatory filing landed 63 days later. 35,879,455 individuals reported across the linked filings. Data reported: Government ID, Authentication, Credentials, and 1 more. Notifications rolled out on a 39-day schedule across 8 filings beginning Dec 18, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
63days

Discovered → first regulatory filing

Discovery variance
94days

Range of discovered_at dates across filings

Filing span
39days

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 >30dVermont⏱ VT AG >14 bdayOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 12dCalifornia✓ CA 60-day OK · 44dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Oct 16, 2023breach begins
Oct 16, 2023discovered · members disagree
notification delay · 63 days
Dec 18, 2023first filing
Jan 26, 2024most 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. DEC 18OR AGOR AG noticefirst filing · states nationwide total 35,879,455day 0
  2. DEC 18WA AGWA AG notice3,100,608 WA residentsday 0
  3. DEC 18ME AGME AG noticestates nationwide total 35,879,455day 0
  4. DEC 18VT AGVT AG noticeno count statedday 0
  5. DEC 18CA AGCA AG noticeno count statedday 0
  6. JAN 26IN AGIN AG noticestates nationwide total 2,302+39d
  7. JAN 26MA AGMA AG notice30 MA residents+39d
  8. JAN 26ME AGME AG noticemost recent · states nationwide total 2,302+39d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 16, 2023 – Oct 19, 2023
OR AG
Discovered
Oct 16, 2023VT AGOct 23, 2023CA AGOct 25, 2023WA AGDec 6, 2023OR AG + ME AGJan 18, 2024ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Identity (basic) · Government ID
WA AG + VT AG + CA AG +2
Attack vector
Unauthorized Access
WA 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)

35,879,455

Sum of filed state slices

3,151,424· 8.8% of stated

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

US35,879,455
WA3,100,608
ME50,782
MA30
IN4

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 filing8 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

39 days

Cadence

~1 / 5.6d

vs. multi-state median

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