Crace Medical Centre
bd_07b16f34c81d95ae · schema v1 · pii pii-v1
Full breach record for Crace Medical Centre →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Knight 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
Post text · scraped from the leak site
30 GB of data. We wait you in the chat.Phone: (02) 6241 0249.Oops, what's all this about? "Nothing happened?", "What do you want us to do?".You have "polite" reception staff. Wait for management in the chat room or we'll start releasing sensitive data from your sources.REMOTE:SERVER:DOCTOR2:DOCTOR1:DOCTOR6:SERVERB:DOCTOR5:REMOTE:RECEPTION1:RECEPTION2:DOCTOR3:DOCTOR7:SERVERB:
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 16, 2023
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.
knight
According to ransomware.live, [Cyclops](group/cyclops) rebrand