National Public Data — December 2023 breach

Clustered 5 filings across 5 jurisdictions · filing window Aug 10, 2024 → Aug 17, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

1,350,684

First → last filing

Aug 10, 2024 → Aug 17, 2024

Merge confidence

100%

incident inc_13e6e4db6bcf448c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Dec 20, 2023–Jul 31, 2024, discovered Dec 30, 2023 — the first regulatory filing landed 224 days later. 1,350,684 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 7-day schedule across 5 filings beginning Aug 10, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

224days

Discovered → first regulatory filing

Filing span

7days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 231dDelaware✓ DE credit monitoring dueFull 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.