Confirmed breach. Intrusion May 6, 2022–May 25, 2022, discovered Nov 23, 2022 — the first regulatory filing landed 23 days later. 2 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 23dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 6, 2022 → May 25, 2022
When the intrusion reportedly occurred, per the linked filings
BerganKDV LTD reported an external system breach that occurred between May 6 and May 25, 2022, and was discovered on November 23, 2022. The breach affected 1,199 individuals, including 2 Maine residents, and compromised names and Social Security Numbers. The company offered 12 months of credit monitoring and identity theft protection services.
Affected (this filing): 2
ME AG ≤30d · 23d
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.