All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

ANTHEM INSURANCE COMPANIES, INC. — December 2014 breach

Clustered 2 filings across 2 jurisdictions · filed Jun 1, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Jun 1, 2015

Merge confidence

100%

incident inc_7d875651c827483d · merged by deterministic · confidence 100%

Part of the ANTHEM INSURANCE COMPANIES, INC. supply-chain incident (2015) — at least 12 organizations filed notifications naming this third party.

Confirmed breach. One breach, 2 legal records. Intrusion Dec 1, 2014, discovered Jan 5, 2015 — the first regulatory filing landed 147 days later. 2 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

147days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

0days

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.

Regulatory clocksCalifornia✓ CA 60-day OK · 31dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 1, 2014breach begins

Jan 5, 2015discovered

notification delay · 147 days

Jun 1, 2015first filing

—watching for filings

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

Member cascade — every filing about this breach

JUN 1NH AGNH AG noticefirst filing · 2 NH residentsday 0
JUN 1CA AGCA AG noticemost recent · no count statedauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Dec 1, 2014
Discovered: Jan 5, 2015· 35d undetected
Data types: Identity (basic) · Government ID · Health (basic) · Employment
Attack vector: Unauthorized Access
Response: Notified federal law enforcement officials · Shared indicators of compromise with the HITRUST C3 · Eliminated any further vulnerability and secured all data

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

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 filing2 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

0 days

vs. multi-state median

20.0× faster

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.