O’Connor
bd_bb4642bc15d96a98 · schema v1 · pii pii-v1
Full breach record for O’Connor →O'Connor Corporation notified New Hampshire residents of a data breach occurring between November 23 and December 1, 2024. An unknown individual accessed systems and potentially viewed or copied personal information. O'Connor detected the incident on December 2, 2024, notified federal law enforcement, and provided 1,314 NH residents with credit monitoring services.
J jump to incidentP pin to compareR raw source
Incident timeline
Nov 23, 2024
Begins
Dec 2, 2024
Discovered
Jan 2, 2025
Scope determined
Jan 31, 2025
Filed
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
- Massachusetts State AGbd_0b379a0dc3244a992025-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 (MA), 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.