Long Beach — November 2023 breach

Clustered 6 filings across 5 jurisdictions · filing window Apr 14, 2025 → Apr 18, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

470,060

First → last filing

Apr 14, 2025 → Apr 18, 2025

Merge confidence

100%

incident inc_c92ea2ff82644708 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Nov 14, 2023, discovered Nov 14, 2023 — the first regulatory filing landed 517 days later (flagged late). 470,060 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

517days

Discovered → first regulatory filing

Discovery variance

490days

Range of discovered_at dates across filings

Filing span

4days

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 clocksWashington✗ WA AG >90dOregon✓ OR AG ≤45dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.