Nottingham Village
bd_1b047c37c2f81f84 · schema v1 · pii pii-v1
Full breach record for Nottingham Village →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 25, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Illinois State AGbd_8f11e7a96415f8e82026-05-01 · +157dCandidate
- Indiana State AGbd_9952bf286179d8c42026-05-22 · +178dVerified
- Massachusetts State AGbd_af10c79872d2b1d82026-05-22 · +178dVerified
- Maine State AGbd_e0f0b0fa313f40752026-05-22 · +178dVerified
Show 2 more filings ↓Show fewer ↑up to 182d gap
- HHS OCRbd_f6267039d415df6d2026-05-22 · +178dVerified by operator
- New Hampshire State AGbd_471f6e396a00c05b2026-05-26 · +182dVerified
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Nov 25, last May 26 (NH) — a 182-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.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.