Clustered 2 filings across 2 jurisdictions · filed Feb 12, 2025. View entity profile → Other incidents for this victim →
incident inc_e2023eacf7e943dd · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · 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.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 25, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 25, 2024
Reported by VERMONT AG, MAINE AG filings
The City of West Haven, Connecticut, disclosed a data incident detected on December 25, 2024, involving unauthorized access to systems containing names and Social Security numbers. The City took systems offline, notified federal law enforcement, and engaged cybersecurity professionals. Affected individuals are offered 24 months of credit monitoring.
On December 25, 2024, the City of West Haven, CT detected suspicious activity on its systems consistent with an external system breach (hacking). The city immediately took systems offline, changed passwords, notified federal law enforcement, and engaged cybersecurity professionals. Potentially impacted information includes names and Social Security numbers. A total of 4,932 individuals were affected, including 1 Maine resident. Experian IdentityWorks credit monitoring was offered for 24 months.
Affected (this filing): 1
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.