Delaware Life — May 2023 breach
Clustered 6 records across 3 jurisdictions: 5 filings and 1 leak-site claim · filing window Sep 6, 2023 → Oct 4, 2023 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_df3e57c9cfdc4028 · merged by human · confidence 100%
Litigation Timing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and leak-site claim in this incident
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JUN 15Leak sitecl0p postfirst record · attacker claim · unverifiedauto-linkedday 0
- SEP 6CA AGCA AG noticeno count statedauto-linked+82d
- SEP 6DE AGDE AG notice1,141 DE residentsauto-linked+82d
- OCT 4CA AGCA AG noticemost recent · no count statedauto-linked+110d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 29, 2023 – May 30, 2023 CA AG
- Discovered
- May 30, 2023IL AGMay 31, 2023CA AGJun 20, 2023IL AGfilings disagree on discovery
- Data types
- Identity (basic) · PII CA AG + DE AG
- Attack vector
- Third-Party / Supply Chain CA AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 26, 2026 · at least one link edge was human-adjudicated
- 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
28 days
Cadence
~1 / 14d
vs. multi-state median
5.6× 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.