Welk Resort Group, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-07-25. The breach occurred on 12/4/2017. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Jul 25, 2018 → Aug 1, 2018. View entity profile → Other incidents for this victim →
incident inc_4aee0e4814d847f6 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 4, 2017
When the intrusion reportedly occurred, per the linked filings
Dec 4, 2017
Reported by CALIFORNIA AG filing
Welk Resort Group, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-07-25. The breach occurred on 12/4/2017. 1 Montana residents were affected.
Affected (this filing): 1
Welk Resort Group, Inc. reported a data breach affecting approximately 1,034 California residents. Unauthorized actors gained access to employee email accounts between November 29 and December 4, 2017, via phishing. Personal information including names, SSNs, driver's licenses, financial account data, and medical history was present in the compromised emails. No evidence of misuse was found. The company engaged forensic investigators and offered 12 months of credit monitoring.
Affected (this filing): 1,034
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.