Clustered 2 filings across 2 jurisdictions · filed Mar 19, 2025. View entity profile → Other incidents for this victim →
incident inc_69585e3d195945c3 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 30, 2025 → Feb 8, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 8, 2025
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Geokon, Inc. notified consumers of a data breach where files containing names and Social Security numbers were copied from its network between Jan 30 and Feb 8, 2025. Suspicious activity was identified on Feb 8, 2025. Geokon secured its environment, investigated, and is offering credit monitoring services. The investigation determined data was accessed but no malware was involved.
Geokon, Inc. notified New Hampshire residents of a data breach where files were copied from its network between Jan 30 and Feb 8, 2025. Suspicious activity was detected on Feb 8, 2025. The incident involved basic PII. Geokon engaged in investigation, enhanced security policies, and offered credit monitoring via CyberScout.
Affected (this filing): 198
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.