A cyber criminal group published data on the night of 20 June 2024 which it claimed belonged to Synnovis and was stolen in the ransomware attack on the laboratory, NHS England said. Synnovis processes blood tests for a number of NHS organisations, primarily in south-east London1. The National Crime Agency and the National Cyber Security Centre were working to verify the data included in the published files1.
NHS England said the attack meant the NHS could not use some of its systems essential to run blood tests in south-east London, and that appointments and operations had been postponed as a result1. All urgent and emergency services, including A&E, urgent care centres and maternity departments, remained open as usual, although there might be some delays where blood tests were required1. Outpatient and community services were mostly running as usual, including cervical screening1.
On the data itself, NHS England said the files were "not simple uploads" and that investigations of this nature were highly complex and could take weeks if not longer1. It said patients should not contact their local hospital or GP practice to ask whether their data had been affected, because those organisations did not hold that information1. An incident helpline was set up on 0345 87789671.
"NHS England has been made aware that a cyber criminal group published data last night which they are claiming belongs to Synnovis and was stolen as part of this attack."
Later statements add detail. On 24 June 2024, NHS England said Synnovis had confirmed through an initial analysis that the published data had been stolen from some of its systems, and that there was at present no evidence the criminals had published a copy of the Laboratory Information Management System where patient test requests and results are stored, although investigations continued3. It said it might be some weeks before it was clear which individuals had been affected3. NHS England's incident page, updated on 10 November 2025, records that the criminals published the stolen files on 20 June 2024, that services were fully restored by December 2024, and that the attack caused delays to over 11,000 outpatient and elective procedure appointments4. It also states that the stolen data may potentially relate to any of Synnovis' service users, including some NHS hospitals, GP practices and clinics across England, while appointment cancellations were confined to south-east London4.
| Date | Development |
|---|---|
| 3 June 2024 | Synnovis suffers a ransomware attack; NHS systems essential to blood testing in south-east London cannot be used1 |
| 20 June 2024 | Criminals publish data files they had stolen in the attack4 |
| 21 June 2024 | NHS England says the NCA and NCSC are working to verify the published data2 |
| 24 June 2024 | Synnovis confirms through initial analysis that published data was stolen from some of its systems3 |
| December 2024 | All Synnovis services available before the attack are restored4 |
| 10 November 2025 | Synnovis says its investigation into the scope of the stolen data is complete and it is contacting impacted customers4 |
Why it matters for households
The published data came from Synnovis' administrative working drive, which supported corporate and business support activities, and is separate from the laboratory database holding the majority of test requests and results5. An initial analysis identified some personal data such as names, NHS numbers and test codes; for some patients it may include a date of birth, and for others test results or numerical values such as blood sugar level5. Not all of the stolen data relates to patients, and where it does the type varies from person to person5.
Synnovis will not contact patients directly; any notification will come from an NHS organisation, which may write to individuals or publish information on its website, and timescales are likely to differ between organisations4. NHS England advises people to be alert to approaches from anyone claiming to have their data, particularly where personal or financial information is requested, and to contact Action Fraud on 0300 123 2040 if contacted by someone making such a claim5. Suspicious emails can be sent to report@phishing.gov.uk and suspicious texts to 77265. NHS England says patients will never be asked for personal or financial information, and that anyone receiving an unexpected message claiming to be from the NHS should check it using contact details from the official organisation's website rather than those in the message5. It also says the incident is no longer causing disruption to patient appointments or services5. The NCSC publishes guidance on data breaches for individuals and families, and its help for individuals and families sets out where to report concerns.
What happens next
Synnovis is contacting its impacted customers, including some NHS hospitals, GP practices and clinics, and each organisation will then review copies of its stolen data to establish what it contains and whether individuals need to take any steps4. NHS England says this assessment may take some time and that organisations may be required to notify the Information Commissioner's Office and contact patients5. Synnovis reported the incident to the Information Commissioner's Office and obtained a legal injunction to prevent people from using or further publishing the data4. NHS England continues to publish updates on its Synnovis incident pages4. The background to the attack and the response of the NHS and regulators are set out in our guides to the Synnovis ransomware incident and how the NHS, government and regulators respond to a major incident.
Sources (5)
- Synnovis Cyber Attack - Statement from NHS England, ashfordstpeters.nhs.uk
- NHS England » Synnovis cyber attack, statement from NHS England, england.nhs.uk
- NHS England » Synnovis cyber attack, statement from NHS England, england.nhs.uk
- NHS England » Synnovis cyber incident, england.nhs.uk
- NHS England » Synnovis cyber incident, public questions and answers, england.nhs.uk

How Services Respond
Synnovis Ransomware and NHS Labs
Your Details in a Data Breach




