All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed4 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

AETNA INC. — June 2020 breach

Clustered 4 filings across 4 jurisdictions · filing window Dec 10, 2020 → Dec 22, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

484,157

First → last filing

Dec 10, 2020 → Dec 22, 2020

Merge confidence

100%

incident inc_af5a879cfea4461f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes unauthorized access. Intrusion Jun 24, 2020–Jul 1, 2020, discovered Jul 1, 2020 — the first regulatory filing landed 162 days later (flagged late). 484,157 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 12-day schedule across 4 filings beginning Dec 10, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

162days

Discovered → first regulatory filing

Filing span

12days

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.

Regulatory clocksOregon✗ OR AG >45dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 24, 2020breach begins

Jul 1, 2020discovered

notification delay · 162 days

Dec 10, 2020first filing

Dec 22, 2020most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

DEC 10OR AGOR AG noticefirst filing · no count statedauto-linkedday 0
DEC 10MA AGMA AG notice5,057 MA residentsauto-linkedday 0
DEC 11IN AGIN AG noticestates nationwide total 484,157auto-linked+1d
DEC 22HHS OCRHHS OCR noticemost recent · states nationwide total 484,157auto-linked+12d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 24, 2020 – Jul 1, 2020
Discovered: Jul 1, 2020· 7d undetected
Data types: Identity (basic) · Government ID · Health (basic) · Financial account
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

484,157

Sum of filed state slices

10,718· 2.2% of stated

98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

12 days

Cadence

~1 / 4d

vs. multi-state median

1.5× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.