Sound Community Bank reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-19. The breach occurred on 08/14/2025. 11 Montana residents were affected.
Affected (this filing): 11
Clustered 2 filings across 2 jurisdictions · filed Nov 19, 2025. View entity profile → Other incidents for this victim →
incident inc_573ac5d87d904c00 · 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
Aug 14, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 14, 2025
Reported by WASHINGTON AG filing
Sound Community Bank reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-19. The breach occurred on 08/14/2025. 11 Montana residents were affected.
Affected (this filing): 11
Sound Community Bank, a finance sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-08-14 and filed notice on 2025-11-19. 5,503 Washington residents were affected. 97 days elapsed between awareness and notification. 0 days to contain the breach.
Affected (this filing): 5,503
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.