DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed5 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

CONTERRA ULTRA BROADBAND HOLDINGS, INC. — March 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Mar 2, 2025 → Jul 18, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

1,497

First → last filing

Mar 2, 2025 → Jul 18, 2025

Merge confidence

100%

incident inc_c2c66e95831447e3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 2 unverified claims. The filing describes a ransomware attack. Intrusion Mar 2, 2025–Mar 12, 2025, discovered Mar 8, 2025 — the first regulatory filing landed 131 days later (flagged late). 1,497 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Notifications rolled out on a 138-day schedule across 3 filings beginning Mar 2, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
131days

Discovered → first regulatory filing

Discovery variance
116days

Range of discovered_at dates across filings

Leak precedence
137days before filing

Days between the first leak-site claim and the first regulatory filing. 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.

Filing span
138days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 131dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 2, 2025breach begins
Mar 8, 2025discovered · members disagree
notification delay · 131 days
Jul 17, 2025first filing
Jul 18, 2025most 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. MAR 2Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. MAR 26Leak siteransomhub postattacker claim · unverified+24d
  3. JUL 17ME AGME AG noticestates nationwide total 1,497+137d
  4. JUL 17MA AGMA AG notice2 MA residents+137d
  5. JUL 18TX AGTX AG noticemost recent · states nationwide total 1,497+138d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 2, 2025 – Mar 12, 2025
ME AG
Discovered
Mar 8, 2025ME AGJul 2, 2025TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
ME AG + TX AG + MA AG
Attack vector
Ransomware
ME 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)

1,497

Sum of filed state slices

380· 25.4% of stated

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

US1,497
TX369
ME9
MA2

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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
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

138 days

Cadence

~1 / 34.5d

vs. multi-state median

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