Clustered 2 filings across 2 jurisdictions · filed May 8, 2026. View entity profile → Other incidents for this victim →
incident inc_8987af6c761f4bf4 · 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 2, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 3, 2026
Reported by NEW HAMPSHIRE AG filing
Cape Fear Country Club reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-05-08. The reporting organization type is Other Commercial. 1 Vermont residents were affected. Categories of data breached: Social Security Numbers, Financial Account Codes, Credit or Debit Account Info.
Cape Fear Country Club notified the New Hampshire Attorney General on May 8, 2026, of a data security incident discovered on January 3, 2026. Unauthorized access occurred on or about January 2, 2026, potentially exposing names, Social Security numbers, and financial account information of 2 New Hampshire residents. The club engaged forensic experts, offered 12 months of credit monitoring, and implemented additional security measures.
Affected (this filing): 2
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.