Clustered 3 filings across 3 jurisdictions · filing window Sep 27, 2024 → Oct 19, 2024. View entity profile → Other incidents for this victim →
incident inc_67f72bbbd8384930 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
NH SC
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 1, 2024
Reported by NEW HAMPSHIRE AG filing
Aiken Electric Co-op, Inc. reported a cybersecurity incident discovered on September 1, 2024, where an unauthorized actor potentially accessed and acquired files from its network. One New Hampshire resident was affected. The company isolated its network, engaged forensic investigators, reset passwords, and offered credit monitoring services.
Affected (this filing): 1
Aiken Electric Co-op, Inc. filed a security breach notice with the South Carolina Office of the Attorney General. The provided PDF document contains only page separators and no substantive incident details, counts, or attack vectors.
About Aiken Electric Cooperative Aiken Electric Cooperative operates in 6 cities and is considered an electricity cooperative. At the moment the company provides electricity to residential, commercial and industrial customer accounts, with ...
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.