Lumexa Imaging
bd_51893610692917a5 · schema v1 · pii pii-v2
Full breach record for Lumexa Imaging →Lumexa Imaging reported to HHS on 2026-05-15 a Hacking/IT Incident affecting 5,830,949 individuals. Breached information located on Network Server. No business associate was involved.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 15, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Oregon State AGbd_24fcdf7525cc1b2c2026-05-15Verified
- HHS OCRbd_2d74a3ba57b9a7e72026-05-15Verified
- Montana State AGbd_8c8f4be9987cfe0d2026-05-15Verified
- Texas State AGbd_1b89348888381ce92026-05-18 · +3dVerified
Show 6 more filings ↓Show fewer ↑up to 28d gap
- South Carolina State AGbd_f8f018a48f8bf5292026-05-18 · +3dVerified
- New Hampshire State AGbd_04a5ed3f1ab847582026-06-12 · +28dVerified
- Washington State AGbd_9572bf4fb8a30cbc2026-06-12 · +28dVerified
- Nebraska State AGbd_b9b9f4915669b3e62026-06-12 · +28dVerified
- Massachusetts State AGbd_d87e7e4891670bc62026-06-12 · +28dVerified
- Vermont State AGbd_f31dffbe7cef33812026-06-12 · +28dVerified
Showing first 10 of 12 linked disclosures.
Filing propagation · 11 filings · 10 states
View merged incident ↗Pattern: first filing May 15 (OR), last Jun 12 (VT) — a 28-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 12 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.