Clustered 2 filings across 2 jurisdictions · filing window Dec 10, 2020 → Dec 22, 2020. View entity profile → Other incidents for this victim →
incident inc_af5a879cfea4461f · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Identity (basic) · Government ID · Health (basic)
CT OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 24, 2020 → Jul 1, 2020
When the intrusion reportedly occurred, per the linked filings
Jul 1, 2020
Reported by OREGON AG filing
Aetna reported a data breach to the Oregon Attorney General. The breach was reported on 2020-12-10. The breach occurred during 6/24/2020 - 7/1/2020. The breach was discovered on 7/1/2020. Notice was sent on 12/10/2020.
Aetna ACE (Health Plan, CT) reported to HHS on 2020-12-22 a Hacking/IT Incident affecting 484,157 individuals. Multiple employees of its business associate experienced a phishing attack compromising ePHI via Email. Exposed data included names, addresses, Social Security numbers, dates of birth, diagnoses, and financial/treatment information. The CE notified HHS, affected individuals, and the media, and revised its BA-related policies and procedures.
Affected (this filing): 484,157
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.