Nottingham Village
bd_f6267039d415df6d · schema v1 · pii pii-v1
Full breach record for Nottingham Village →Nottingham Village reported to HHS on 2026-05-22 a Hacking/IT Incident affecting 5240 individuals. Breached information located on Network Server.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 22, 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?Ransomware claims (1)
- Leak Siteqilinbd_1b047c37c2f81f842025-11-25 · +178dCandidate
Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_9952bf286179d8c42026-05-22Verified
- Massachusetts State AGbd_af10c79872d2b1d82026-05-22Verified
- Maine State AGbd_e0f0b0fa313f40752026-05-22Verified
- New Hampshire State AGbd_471f6e396a00c05b2026-05-26 · +4dVerified
Show 1 more filing ↓Show fewer ↑up to 21d gap
- Illinois State AGbd_8f11e7a96415f8e82026-05-01 · +21dCandidate
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing May 1 (IL), last May 26 (NH) — a 25-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.