Clustered 3 filings across 2 jurisdictions · filing window Jun 28, 2022 → Aug 8, 2022. View entity profile → Other incidents for this victim →
incident inc_6a2d7ffe0aec469c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT
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.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Aug 9, 2021
When the intrusion reportedly occurred, per the linked filings
Aug 9, 2021
Reported by MAINE AG filings
Smith, Gambrell, & Russell, LLP reported an external system breach (hacking) occurring on August 9, 2021. The incident compromised names and driver's license numbers of 6,515 individuals, including 1 Maine resident. Notification was sent on June 28, 2022, offering 12 months of credit monitoring and identity restoration services.
Affected (this filing): 6,515
Smith, Gambrell & Russell, LLP reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-28. The breach occurred on 8/9/2021. 21 Montana residents were affected.
Affected (this filing): 21
The law firm Smith, Gambrell & Russell, LLP experienced an external system breach on August 9, 2021, discovered the same day. The breach compromised the names and Social Security numbers of 19,322 individuals. The firm notified affected individuals on August 8, 2022, and offered 12 months of credit monitoring and identity restoration services through IDX.
Affected (this filing): 19,322
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.