Landmark Admin — May 2024 breach

Clustered 2 filings across 2 jurisdictions · filing window Mar 24, 2025 → Apr 1, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge95%

Determination

Confirmed

Members

2 filings

States

Affected · reported

—

First → last filing

Mar 24, 2025 → Apr 1, 2025

Merge confidence

95%

incident inc_2693ad915f054718 · merged by deterministic · confidence 95%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes a ransomware attack. Intrusion May 13, 2024–Jun 17, 2024, discovered May 13, 2024 — the first regulatory filing landed 315 days later. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

315days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

8days

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.

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.