O'Brien & Ryan LLP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-08 and was reported on 2025-09-09. 4 Indiana residents were affected. 584 individuals affected in total.
Affected (this filing): 584
Clustered 2 filings across 2 jurisdictions · filing window Sep 9, 2025 → Sep 10, 2025. View entity profile → Other incidents for this victim →
incident inc_aad240a77a8b4db3 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 8, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 8, 2025
Reported by NEW HAMPSHIRE AG filing
O'Brien & Ryan LLP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-08 and was reported on 2025-09-09. 4 Indiana residents were affected. 584 individuals affected in total.
Affected (this filing): 584
O'Brien & Ryan, LLP, a law firm, notified the New Hampshire Attorney General on September 10, 2025, of a data event affecting 3 state residents. The firm became aware of unauthorized access and copying of files containing names and Social Security numbers on April 8, 2025. The firm engaged outside cybersecurity specialists, notified federal law enforcement, and provided 12 months of credit monitoring to affected individuals.
Affected (this filing): 3
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.