O’Connor
bd_0b379a0dc3244a99 · schema v1 · pii pii-v1
Full breach record for O’Connor →O’Connor Corporation reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2025-01-31. 4,519 Massachusetts residents were affected.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jan 31, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siteqilinbd_fcd96e9b31fe877c2025-09-25 · +237dVerified by operator
- Leak Siteqilinbd_4907e4afb9c35d432025-09-06 · +218dVerified by operator
Regulatory filings (7) · sorted by filing gap
- New Hampshire State AGbd_bb4642bc15d96a982025-01-31Verified
- Vermont State AGbd_c1e7b99bdc36957f2025-01-31Verified
- Montana State AGbd_c8258b8b3d9339542025-01-31Candidate
- Maine State AGbd_d265cedd5041da622025-01-31Verified
Show 3 more filings ↓Show fewer ↑up to 10d gap
- Nebraska State AGbd_e6b2240d202fd1072025-01-31Verified
- Indiana State AGbd_effd7150d1f946492025-01-31Verified
- Rhode Island State AGbd_932a8731708f66b92025-02-10 · +10dVerified
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Jan 31 (NH), last Feb 10 (RI) — a 10-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.