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

Confirmed3 filings · 1 stateUnverified claimConfirmedEnforcedransomhouse

Merged incident · 3 filings

Delaware Life — February 2023 breach

Clustered 3 filings across 2 jurisdictions · filing window Feb 12, 2023 → Jul 28, 2023. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

—

First → last filing

Feb 12, 2023 → Jul 28, 2023

Merge confidence

100%

incident inc_fe65c21c04324392 · merged by deterministic · confidence 100%

Confirmed breach. Intrusion Feb 9, 2023, discovered Feb 9, 2023 — the first regulatory filing landed 169 days later.

Litigation Timing

Notification delay

169days

Discovered → first regulatory filing

Leak precedence

165days 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

165days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Incident timeline

Feb 9, 2023breach begins

Feb 9, 2023discovered

notification delay · 169 days

Jul 28, 2023first & only 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

FEB 12Leak sitedispossessor postfirst filing · attacker claim · unverifiedauto-linkedday 0
MAR 11Leak siteransomhouse postattacker claim · unverifiedauto-linked+27d
JUL 28HI AGHI AG noticemost recent · no count stated+165d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 9, 2023
Discovered: Feb 9, 2023
Data types: Identity (basic) · Government ID
Attack vector: Ransomware
Response: Took steps to isolate and secure systems · Retained a leading third-party forensics firm to conduct a thorough investigation · Alerted appropriate regulatory authorities

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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

165 days

Cadence

~1 / 82.5d

vs. multi-state median

33.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.