DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteSEC 8-KState AGConfirmed13 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 13 records

Frontier Communications Parent, Inc. — April 2024 breach

Clustered 13 records across 12 jurisdictions: 12 filings and 1 leak-site claim · filing window Apr 18, 2024 → Jun 12, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 records

States

11

Affected · reported

751,895

First → last dated filing

Apr 18, 2024 → Jun 12, 2024

Merge confidence

100%

incident inc_3a32c0e1d9e54495 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Apr 13, 2024–Apr 16, 2024, discovered Apr 14, 2024 — the first regulatory filing landed 4 days later; 1 later filing was flagged late. 751,895 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 55-day schedule across 11 dated filings beginning Apr 18, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
4days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 47d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Materiality delta
1days

Discovery to SEC materiality determination

SEC filing delay
3days

Materiality determination to SEC 8-K filing

Filing span
55days

Time between earliest and latest filing

Regulatory clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 53dSEC✓ SEC 4-day OK · 3dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 13, 2024breach begins
Apr 14, 2024discovered
notification delay · 4 days
Apr 18, 2024first dated filing
Jun 12, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. APR 18SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUN 1Leak siteransomhub postattacker claim · unverified+44d
  3. JUN 1IL AGIL AG noticefiling day not on record · no count stated—
  4. JUN 6WA AGWA AG notice8,211 WA residents+49d
  5. JUN 6VT AGVT AG noticeno count stated+49d
  6. JUN 6ME AGME AG noticestates nationwide total 751,895+49d
  7. JUN 6IN AGIN AG noticestates nationwide total 751,895+49d
  8. JUN 6MT AGMT AG notice279 MT residents+49d
  9. JUN 11CA AGCA AG noticeno count stated+54d
  10. JUN 11OR AGOR AG noticestates nationwide total 751,895+54d
  11. JUN 12MA AGMA AG notice671 MA residents+55d
  12. JUN 12NH AGNH AG notice120 NH residents+55d
  13. JUN 12SC AGSC AG noticemost recent · 7,534 SC residents+55d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 13, 2024 – Apr 16, 2024
WA AG
Discovered
Apr 14, 2024· 1d undetected
SEC 8-K + IL AG + WA AG +7
Data types
Identity (basic) · Government ID · PII
SEC 8-K + WA AG + MT AG +6
Attack vector
Unauthorized Access
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)

751,895

Sum of filed state slices

42,814· 5.7% of stated

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

US751,895
IN25,860
WA8,211
SC7,534
MA671
MT279
ME139
NH120

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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 22, 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

55 days

Cadence

~1 / 5.5d

vs. multi-state median

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