Confirmed breach. Intrusion Jan 8, 2021, discovered Jul 22, 2021 — the first regulatory filing landed 106 days later (flagged late). 38,653 individuals reported across the linked filings.
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.
Regulatory clocksMaine✗ ME AG >90d · 110dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
38,653
Data types
—
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 22, 2021
When the intrusion reportedly occurred, per the linked filings
CopperPoint Insurance Company, Pacific Compensation Insurance Company, and Alaska National Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-05. The breach occurred on 7/22/2021. 8 Montana residents were affected.
Affected (this filing): 8
🦞Maine State AGMost recentlinked via multistate filing link · 100%
CopperPoint Insurance Company, Pacific Compensation Insurance Company, and Alaska National Insurance reported an external system breach (hacking) occurring on January 8, 2021, discovered on July 22, 2021. The incident compromised names and Social Security Numbers of 38,653 individuals, including 2 Maine residents. Written notification was sent on November 5, 2021, offering 12 months of identity protection services.
Affected (this filing): 38,653
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.