DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed16 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 16 filings

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

9

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

Sensitive data

identity_government

Incident timeline

May 13, 2024breach begins
May 13, 2024discovered
notification delay · 30 days
Jun 12, 2024first filing
Apr 11, 2025most recent filing

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

Member cascade — every filing about this breach

  1. JUN 12ME AGME AG noticefirst filing · 0 affectedday 0
  2. JUN 16ME AGME AG notice0 affected+4d
  3. JUN 27MT AGMT AG notice2,987 MT residents+15d
  4. JUN 27VT AGVT AG noticeno count stated+15d
  5. JUN 27ME AGME AG notice1 ME residents+15d
  6. OCT 23VT AGVT AG noticeno count stated+133d
  7. OCT 23OR AGOR AG noticeno count stated+133d
  8. OCT 23IN AGIN AG noticestates nationwide total 806,519+133d
  9. OCT 23ME AGME AG noticestates nationwide total 806,519+133d
  10. OCT 23CA AGCA AG noticeno count stated+133d
  11. OCT 23WA AGWA AG notice4,795 WA residents+133d
  12. OCT 23DE AGDE AG noticeno count stated+133d
  13. OCT 28NH AGNH AG notice335 NH residents+138d
  14. APR 11CA AGCA AG noticeno count stated+303d
  15. APR 11WA AGWA AG notice11,691 WA residents+303d
  16. APR 11ME AGME AG noticemost recent · states nationwide total 1,613,773+303d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 13, 2024
ME AG
Discovered
May 13, 2024
ME AG + MT AG + VT AG +5
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MT AG + VT AG +4
Attack vector
Unauthorized Access
ME AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,613,773

Sum of filed state slices

27,291· 1.7% of stated

98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US1,613,773
WA11,691
IN10,750
MT2,987
ME1,528
NH335

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing16 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 10, 2026 · 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

303 days

Cadence

~1 / 20.2d

vs. multi-state median

37.9× 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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.