Breach Watch
NSW Health — Credential compromise disclosed November 2026
Information about patients was involved in a credential compromise at NSW Health, disclosed on 4 November 2026.
People affected: 100,000, stated by the source.
The sources for this record do not confirm when the incident happened.
- Credential compromise
- Independently corroborated
- Disclosure date: 4 November 2026
What matters
- Who was affected
- Patients
- People affected
- 100,000, stated by the source
- Information involved
- Sensitive documents
- Authorities notified
- Cyber Security NSW and NSW Police
Key dates
- Incident date
- Not confirmed
- Discovery date
- Not confirmed
- Disclosure date
- 4 November 2026
- Notification date
- Not confirmed
Each date is either established by a quoted source or explicitly not confirmed.
Affected people and data
Categories of affected data
- Other information
- sensitive documents
Grouped by Cleverer for reading. Each item is worded as the source states it.
Notifications and response
Regulators notified
- Cyber Security NSW
Police notified
- NSW Police
What the organisation says it did
- commenced an investigation
Not stated: Remediation stated
Sources
Each source is labelled by what it is: the organisation's own statement, a regulator's publication, or a news report. Follow the link to read the original.
Original report
Police investigate cybersecurity breach of NSW Health's Oral Health Fee For Service Scheme website - ABC News
Further sources
Corroborating report
NSW Health data breach: Detectives investigate alleged theft of 100,000 sensitive documents
Corroborating report
NSW Police launch Strike Force Civic investigation into NSW Health cyber breach - Australian Cyber Security Magazine
For people who may be affected
If you may be affected
This record does not yet cite a notice from NSW Health with instructions for affected people. If you have been told you are affected, follow the instructions in that notice, and reach the organisation through contact details on its own website.
Practical steps
- Treat unexpected calls, texts and emails that mention this incident with caution. Contact the organisation using details you find yourself, not details in the message.
- Keep a note of any notice you receive and anything you do in response. It helps if you need to make a complaint or claim later.
Official help
- Office of the Australian Information CommissionerRespond to a data breach notification Steps for contact, financial and identity information, from the privacy regulator.
- Office of the Australian Information CommissionerData breach support and resources Support services, including mental health support.
Cleverer is not connected with NSW Health and cannot tell you whether your information was involved. Only the organisation can confirm that.
For Australian businesses
What would your business need to prove after an incident like this?
This record is classed as credential compromise. Incidents of that kind raise questions any business holding personal information should be able to answer with records, not recollection. This is not a finding about the organisation in this record. It is what another business would want on file if the same thing happened to it.
MFA coverage records
Showing which accounts required multi-factor authentication, and from when.
Access reviews
Showing that you regularly confirm who can reach what, and remove what they no longer need.
Offboarding records
Showing that departing staff and contractors lost access on the day they left.
Password and account policy
Showing the rules you set, and when they were last reviewed.
Phishing awareness records
Showing which staff completed training, and when.
Notification decision records
Showing how you assessed whether the breach was notifiable, and when you decided.
Could your business prove what it had in place?
A policy shows what you intended. Evidence shows what happened. Check your current cyber compliance position and see which evidence is missing.
Cleverer helps businesses keep this work current and retain dated evidence of what was actually done. It does not prevent breaches, and nothing on this page is a finding about how this incident happened or what the organisation in this record did.