Landmark Admin — May 2024 breach

Clustered 16 filings across 9 jurisdictions · filing window Jun 12, 2024 → Apr 11, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

16 filings

States

Affected · reported

1,613,773

First → last filing

Jun 12, 2024 → Apr 11, 2025

Merge confidence

100%

incident inc_c9e748a5644c4592 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings. Intrusion May 13, 2024–Jun 17, 2024, discovered May 13, 2024 — the first regulatory filing landed 30 days later (flagged late). 1,613,773 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 303-day schedule across 16 filings beginning Jun 12, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

30days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

303days

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 clocksMaine✗ ME AG >90d · 163dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 163dWashington✗ WA AG >90dFull 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.