Town of Apex — June 2024 breach

Clustered 5 filings across 4 jurisdictions · filing window Mar 30, 2026 → Apr 6, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

22,601

First → last filing

Mar 30, 2026 → Apr 6, 2026

Merge confidence

100%

incident inc_e6d771f022f64293 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a ransomware attack. Intrusion Jun 23, 2024–Jul 2, 2024, discovered Jul 2, 2024 — the first regulatory filing landed 636 days later (flagged late). 22,601 individuals reported across the linked filings. Data reported: Identity (basic), Employment, and PII. Notifications rolled out on a 7-day schedule across 5 filings beginning Mar 30, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

636days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

7days

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 clocksMassachusetts✗ MA 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.