O’Connor — November 2024 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 31, 2025 → Feb 10, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

11,644

First → last dated filing

Jan 31, 2025 → Feb 10, 2025

Merge confidence

100%

incident inc_60031453e8054b5d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Nov 23, 2024–Dec 1, 2024, discovered Dec 2, 2024 — the first regulatory filing landed 60 days later. 11,644 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Notifications rolled out on a 10-day schedule across 7 dated filings beginning Jan 31, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

60days

Discovered → first regulatory filing

Discovery variance

53days

Range of discovered_at dates across filings

Filing span

10days

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 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 7dFull 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.