Confirmed breach. Intrusion Oct 6, 2025, discovered Oct 14, 2025 — the first regulatory filing landed 27 days later. 3,874 individuals reported across the linked filings.
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.
Regulatory clocksMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
3,874
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 6, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Oct 14, 2025
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Hampton Roads Sanitation District reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-06 and was reported on 2025-11-10. 1 Indiana residents were affected. 3,874 individuals affected in total.
Hampton Roads Sanitation District, a government entity, reported a data breach affecting 2 Maine residents. The breach, an external system hacking incident, was discovered on October 14, 2025, after occurring on October 6, 2025. Affected individuals were notified on November 10, 2025, and offered 12 months of complimentary credit monitoring and identity theft restoration services.
Affected (this filing): 2
ME AG ≤30d · 29d
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.