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

Confirmed4 filings · 2 statesUnverified claimConfirmedEnforcedcl0plow sensitivity

Merged incident · 4 filings

Delaware Life — May 2023 breach

Clustered 4 filings across 3 jurisdictions · filing window Jun 15, 2023 → Oct 4, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

—

First → last filing

Jun 15, 2023 → Oct 4, 2023

Merge confidence

100%

incident inc_df3e57c9cfdc4028 · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 93 organizations filed notifications naming this third party.

Confirmed breach. One breach, 3 legal records and 1 unverified claim. Intrusion May 29, 2023–May 30, 2023, discovered May 31, 2023 — the first regulatory filing landed 98 days later (flagged late). Notifications rolled out on a 110-day schedule across 3 filings beginning Jun 15, 2023. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

98days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

82days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

110days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 98dFull clock table in Litigation Timeline

Incident timeline

May 29, 2023breach begins

May 31, 2023discovered

notification delay · 98 days

Sep 6, 2023first filing

Oct 4, 2023most recent filing

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

Member cascade — every filing about this breach

JUN 15Leak sitecl0p postfirst filing · attacker claim · unverifiedauto-linkedday 0
SEP 6CA AGCA AG noticeno count statedauto-linked+82d
SEP 6DE AGDE AG noticeno count statedauto-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
Discovered: May 31, 2023· 2d undetected
Data types: PII · Identity (basic)
Attack vector: Third-Party / Supply Chain
Response: Launched an investigation into the nature and scope of the MOVEit vulnerability’s impact on our systems · Conducted a manual review of our records to confirm the identities of individuals potentially affected · Patched servers

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-confirmed · 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

110 days

Cadence

~1 / 36.7d

vs. multi-state median

22.0× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.