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

Confirmed3 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

METROPOLITAN LIFE INSURANCE CO — November 2023 breach

Clustered 3 filings across 2 jurisdictions · filing window Mar 28, 2024 → Apr 23, 2024. View entity profile → Other incidents for this victim →

✓ affected count, data types agreeMerge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

13,811

First → last filing

Mar 28, 2024 → Apr 23, 2024

Merge confidence

100%

incident inc_c11b5f124ed24067 · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe an accidental exposure. Intrusion Nov 1, 2023–Feb 5, 2024, discovered Jan 18, 2024 — the first regulatory filing landed 70 days later (flagged late). 13,811 individuals reported across the linked filings. Data reported: Government ID, PHI, Identity (basic), and 1 more. Notifications rolled out on a 26-day schedule across 3 filings beginning Mar 28, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

70days

Discovered → first regulatory filing

Filing span

26days

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 clocksTexas✗ TX AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 1, 2023breach begins

Jan 18, 2024discovered

notification delay · 70 days

Mar 28, 2024first filing

Apr 23, 2024most recent filing

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

Member cascade — every filing about this breach

MAR 28CA AGCA AG noticefirst filing · no count statedday 0
APR 22CA AGCA AG noticeno count statedauto-linked+25d
APR 23TX AGTX AG noticemost recent · states nationwide total 13,811+26d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 1, 2023
Discovered: Jan 18, 2024· 78d undetected
Data types: Health (basic) · Identity (basic) · Government ID · PHI

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)

13,811

Sum of filed state slices

1,440· 10.4% of stated

90% 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 filing3 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: llm
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

26 days

Cadence

~1 / 13d

vs. multi-state median

3.3× 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.