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

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

No cross-filing comparison data available for this incident.

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.