Erickson Demel & Associates, PllC reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-08. The breach occurred from 1/9/2023 to 1/14/2023. 4 Montana residents were affected.
Affected (this filing): 4
Clustered 2 filings across 2 jurisdictions · filed Mar 8, 2023. View entity profile → Other incidents for this victim →
incident inc_58ceb8c756b94ced · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 9, 2023
When the intrusion reportedly occurred, per the linked filings
Jan 14, 2023
Reported by MAINE AG filing
Erickson Demel & Associates, PllC reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-08. The breach occurred from 1/9/2023 to 1/14/2023. 4 Montana residents were affected.
Affected (this filing): 4
Erickson Demel & Associates, PLLC, a financial services firm, reported a data breach affecting 3,007 individuals, including one Maine resident. The breach, which occurred on January 9, 2023, and was discovered on January 14, 2023, was an external system breach (hacking). The compromised information included names in combination with Social Security numbers. The company notified affected individuals on March 8, 2023, and offered 24 months of free credit monitoring services through Experian.
Affected (this filing): 1
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.