Clustered 3 filings across 3 jurisdictions · filing window Jun 2, 2021 → Jul 16, 2021. View entity profile → Other incidents for this victim →
incident inc_93e6552f8e0649d1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT 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
Mar 1, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 1, 2021
Reported by WASHINGTON AG, MAINE AG filings
Asarco, LLC, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2021-03-01 and filed notice on 2021-06-02. 670 Washington residents were affected. 93 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 670
ASARCO LLC reported an external system breach that occurred and was discovered on March 1, 2021. The breach affected 9 Maine residents, compromising their names and driver's license or non-driver identification card numbers. The company offered affected individuals a 12-month membership to NortonLifeLock Defender Choice for identity theft protection.
Affected (this filing): 9
Asarco LLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-07-16. The breach occurred on 3/1/2021. 576 Montana residents were affected.
Affected (this filing): 576
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.