Clustered 2 filings across 2 jurisdictions · filing window Jan 19, 2024 → Jan 23, 2024. View entity profile → Other incidents for this victim →
incident inc_8fda72a5663b4847 · 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.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 22, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 26, 2023
Reported by VERMONT AG, MAINE AG filings
Newington Fire Department notified Vermont AG of a cybersecurity incident affecting personal information (name, SSN) of individuals on or about September 22, 2023. The department secured the network, notified law enforcement, and engaged outside cybersecurity professionals. Affected individuals were offered 12 months of Experian IdentityWorks.
The Newington Fire Department reported a data breach affecting 127 individuals, including 16 Maine residents. The breach, which occurred on September 22, 2023, and was discovered on December 26, 2023, was described as an external system breach (hacking). The compromised information includes names or other personal identifiers in combination with Social Security Numbers. Affected individuals were notified on January 19, 2024, and offered 12 months of credit monitoring services through Experian IdentityWorks 3B.
Affected (this filing): 16
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.