Confirmed breach. Intrusion Jan 25, 2023–Nov 6, 2023, discovered Oct 1, 2023 — the first regulatory filing landed 368 days later. 2 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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
NH VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 25, 2023 → Nov 6, 2023
When the intrusion reportedly occurred, per the linked filings
249 days
Breach discovered
Oct 1, 2023
Reported by NEW HAMPSHIRE AG filing
368 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
ServiceChannel.com, Inc. notified the NH Attorney General of unauthorized access by third parties between Jan 25 and Nov 6, 2023. The breach affected personal information of 2 NH residents. ServiceChannel engaged forensic experts, notified law enforcement, enhanced security controls, and offered credit monitoring to affected individuals.
ServiceChannel.com notified consumers in Vermont and Rhode Island of a data breach involving unauthorized access to customer accounts. The incident compromised names, addresses, and Social Security numbers. The company offered 12 months of credit monitoring and established an incident response hotline. The investigation is ongoing.
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.