Lake Kennedy McCulloch CPA's reported a data breach to the Montana Attorney General. The breach was reported on 2017-04-07. The breach occurred from 1/30/2017 to 2/11/2017. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Apr 7, 2017 → Apr 9, 2017. View entity profile → Other incidents for this victim →
incident inc_bafe9c94fed6452c · 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.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 30, 2017
When the intrusion reportedly occurred, per the linked filings
Feb 11, 2017
Reported by WASHINGTON AG filing
Lake Kennedy McCulloch CPA's reported a data breach to the Montana Attorney General. The breach was reported on 2017-04-07. The breach occurred from 1/30/2017 to 2/11/2017. 7 Montana residents were affected.
Affected (this filing): 7
Lake Kennedy McCulluch CPAs PS, a finance sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2017-02-11 and filed notice on 2017-04-09. 1,688 Washington residents were affected. 57 days elapsed between awareness and notification. 12 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 1,688
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.