Confirmed breach. Intrusion Jun 23, 2024, discovered Jul 2, 2024 — the first regulatory filing landed 636 days later (flagged late). 972 individuals reported across the linked filings.
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 >90d · 636dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
972
Data types
—
Jurisdictions
2
ME NC
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 23, 2024
When the intrusion reportedly occurred, per the linked filings
The Town of Apex, North Carolina reported an external system breach (hacking) that occurred on June 23, 2024 and was discovered on July 2, 2024. A total of 22,601 individuals were affected, including 2 Maine residents. Consumer notifications were sent on March 30, 2026. No identity theft protection services were offered.
Affected (this filing): 2
ME AG >90d · 636dME resident >180d · 636d
🇺🇸NCHHS OCRMost recentlinked via same-victim cross-source · 100%
Town of Apex, North Carolina (a Health Plan entity) reported a Hacking/IT Incident affecting 970 individuals to HHS OCR on March 30, 2026. The breach involved a network server. No business associate was involved.
Affected (this filing): 970
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.