Clustered 3 filings across 3 jurisdictions · filing window Nov 12, 2025 → Dec 15, 2025. View entity profile → Other incidents for this victim →
incident inc_5f86bc0921634fae · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
MT OR WA
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
Jun 19, 2025
When the intrusion reportedly occurred, per the linked filings
Jun 19, 2025
Reported by WASHINGTON AG, OREGON AG filings
Hamilton Construction Company reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-12. The breach occurred from 06/19/2025 to 10/07/2025. 21 Montana residents were affected.
Affected (this filing): 21
Hamilton Construction Company, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-06-19 and filed notice on 2025-11-12. 610 Washington residents were affected. 146 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 610
Hamilton Construction Company reported a data breach to the Oregon Attorney General. The breach was reported on 2025-12-15. The breach occurred during 6/19/2025 - 6/19/2025. The breach was discovered on 6/19/2025. 2,667 individuals were affected. Notice was sent on 11/12/2025.
Affected (this filing): 2,667
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.