Clustered 2 filings across 2 jurisdictions · filed May 18, 2026. View entity profile → Other incidents for this victim →
incident inc_ecc05b2334714699 · 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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 7, 2026 → Jan 14, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 14, 2026
Reported by NEW HAMPSHIRE AG filing
The Beacon Mutual Insurance Company reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-05-18. The reporting organization type is Insurance. 195 Vermont residents were affected. Categories of data breached: Social Security Numbers, Government ID Numbers, Health Records.
The Beacon Mutual Insurance Company notified the New Hampshire Attorney General of a cybersecurity incident affecting approximately 646 NH residents. Unauthorized access occurred between January 7 and January 14, 2026, resulting in the exfiltration of names and Social Security numbers. Beacon Mutual contained the incident, reported to law enforcement, and is offering credit monitoring services to affected individuals.
Affected (this filing): 646
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.