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

Forum Communications Company — January 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Mar 14, 2025 → Mar 19, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

28,830

First → last filing

Mar 14, 2025 → Mar 19, 2025

Merge confidence

100%

incident inc_54d521f254d047c4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Jan 14, 2025–Jan 31, 2025, discovered Jan 14, 2025 — the first regulatory filing landed 59 days later. 28,830 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 5-day schedule across 8 filings beginning Mar 14, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
38days

Range of discovered_at dates across filings

Filing span
5days

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 clocksVermont⏱ VT AG >14 bdayMaine✓ ME AG ≤30d · 26dMaryland✓ MD AG ≤30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 14, 2025breach begins
Jan 14, 2025discovered · members disagree
notification delay · 59 days
Mar 14, 2025first filing
Mar 19, 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 14IN AGIN AG noticefirst filing · states nationwide total 28,830day 0
  2. MAR 19MT AGMT AG notice43 MT residents+5d
  3. MAR 19NE AGNE AG noticeno count stated+5d
  4. MAR 19ME AGME AG noticestates nationwide total 28,830+5d
  5. MAR 19MD AGMD AG notice12 MD residents+5d
  6. MAR 19VT AGVT AG noticeno count stated+5d
  7. MAR 19MA AGMA AG notice10 MA residents+5d
  8. MAR 19NH AGNH AG noticemost recent · 5 NH residents+5d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 14, 2025
IN AG
Discovered
Jan 14, 2025NE AGJan 31, 2025VT AG + NH AGFeb 21, 2025ME AG + MD AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MT AG + NE AG + VT AG +4
Attack vector
Unauthorized Access
MT 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)

28,830

Sum of filed state slices

98· 0.3% of stated

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

US28,830
MT43
IN26
MD12
MA10
NH5
ME2

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
deterministic
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

5 days

Cadence

~1 / 0.7d

vs. multi-state median

1.6× faster

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.