Nov 16, 2026 · 8 min read
1,371 Cyber Incidents Reported to UK ICO, a Quarterly Record
Between July and September 2026, UK organisations told the Information Commissioner's Office about more cyber incidents than in any quarter on record, and about 4,604 personal data breaches in total. The regulator opened investigations into 18 of the cyber cases. About 70% of all reports were not cyberattacks, a category that includes emails sent to the wrong recipient.
The UK's data protection regulator has just published its busiest quarter for cyber incidents. Organisations reported 1,371 cyber incidents to the Information Commissioner's Office (ICO) from July to September 2026, beating a quarterly record set in 2023, according to an analysis of ICO data by The Record published on November 13. Total breach reports hit a quarterly high of 4,604. For compliance teams, the headline number hides a more useful one: roughly seven in ten of those reports were not cyberattacks at all, and email mistakes are among the most familiar of them.
Key Takeaways
- The ICO received 1,371 cyber incident reports in Q3 2026 (July to September), a record for any three month period, and 4,604 personal data breach reports overall, according to The Record.
- Retail and manufacturing reported the most incidents, rising from 205 in Q2 to 296 in Q3, while charity and voluntary sector reports climbed from 79 to 145.
- Ransomware reports to the ICO fell to 102 in Q3 2026, even as about 350 UK organisations have been named on extortion leak sites so far this year.
- The ICO opened investigations into 18 of the 1,371 Q3 cyber incidents, about 1.3%, and closed most cases with informal action.
- Email mistakes remain a large source of breaches: an analysis of ICO data counted 2,459 misdirected email incidents in 2025, and the ICO reprimanded the Metropolitan Police in July 2026 over a To field that should have been BCC.
How Many Cyber Incidents Were Reported to the ICO in Q3 2026?
UK organisations reported 1,371 cyber incidents to the ICO in the third quarter of 2026, the highest quarterly figure in the regulator's dataset. The ICO's data security incident trends page shows the dataset was updated to Q3 2026 on 26 October 2026. The Record says 2026 is on course to beat the full year record set in 2023.
The 4,604 total covers every personal data breach report, including what the ICO files as incidents that were not cyber related. The Record gives "emails sent to the wrong recipient" as its example. Subtraction puts those at about 3,233, or 70% of the total.
Most of the cyber reports do not land in a neat bucket. According to The Record, the largest share is classed as "other cyber incidents," a catch all separate from phishing, ransomware and malware.
Which Sectors Reported the Most Incidents?
Retail and manufacturing reported the most incidents in Q3 2026, with 296, up from 205 in Q2. The Record's breakdown of the six most affected sectors shows sharp growth almost everywhere:
- Retail and manufacturing: 205 to 296, a 44% rise
- Charities and voluntary organisations: 79 to 145, an 84% rise
- Online technology and telecoms: 76 to 120, a 58% rise
- Education and childcare: 135 to 115, the only one of the six to fall
The charity figure stands out. The ICO warns on its trends page that sector labels are assigned "as a best fit" and that the way it inputs data "changes over time," so quarter to quarter swings deserve caution. Still, a jump of 66 reports is hard to explain as a coding quirk alone.
Why Are Ransomware Reports Falling While Attacks Rise?
Ransomware reports to the ICO have fallen every year since 2023, with 2026 on pace to drop again, even though leak site data shows extortion attacks on UK organisations rising. The Record lists the ICO's ransomware counts as 1,253 in 2023, 752 in 2024, 620 in 2025 and 321 for January to September 2026, with 111 in Q2 and 102 in Q3.
Leak sites tell a different story. About 350 UK organisations have been named on criminal leak sites so far in 2026, roughly 50% more than last year, compared with a global rise closer to 25%, according to the same report. Rafe Pilling of Sophos called leak site data an "imperfect metric" but said: "Globally, this is a recent surge. In the UK it has been a steady climb all year." Groups named as drivers include Qilin and The Gentlemen.
Two explanations fit, and neither is reassuring. The Record notes it is unclear whether the ICO's ransomware category includes pure data extortion, where nothing is encrypted. If those cases are filed as "other cyber incidents," the record 1,371 is partly ransomware under another name. If they are not reported at all, the gap between 102 ICO reports and a leak site count rising 50% is a reporting problem. Either way, ransomware's share of the regulator's cyber caseload, about 7% in Q3, understates the risk a security team should plan for.
What Is the ICO Doing About It?
Very little of the Q3 caseload will end in formal enforcement. The Record reports the ICO pursued investigations in 18 of the 1,371 cyber incidents, about 1 in 76, and closed most cases with informal action. An ICO spokesperson said: "Cyber attacks continue to be a significant threat to organisations across all sectors."
The fines that do land show what the regulator cares about. On 7 May 2026 the ICO fined South Staffordshire Plc and South Staffordshire Water Plc £963,900 under Articles 5(1)(f) and 32(1) of the UK GDPR, after personal data on roughly 633,887 people was exfiltrated. The penalty notice traces initial access to 11 September 2020, when a malicious attachment in a phishing email installed a remote access trojan. The attacker then sat dormant until May 2022. Elsewhere, the ICO has leaned on reprimands, including one against the criminal records office ACRO in August 2026, which we covered in our ACRO breach report. Its 2026 penalties also include £14.47 million against Reddit for children's privacy failures, not a security breach.
Why Email Users Should Care
Email is where both halves of the ICO's data meet. On the cyber side, phishing remains a common way in: the South Staffordshire attack began with one opened attachment. On the other side, the ICO's glossary of incident types lists "Data emailed to incorrect recipient" and "Failure to use bcc" as categories of their own. An analysis of ICO data by the security firm Bridewell, reported by IT Brief UK, counted 2,459 misdirected email incidents in 2025, up 62% from 1,519 in 2020.
The Metropolitan Police case shows how small the mistake can be. On 29 November 2024, an officer emailed people targeted in the "Honeytrap" scheme, unsolicited WhatsApp messages aimed at people with links to Parliament, to say a suspect's bail date had moved. The addresses went in the To field. According to the ICO's reprimand and enforcement notice of 27 July 2026, the email exposed 18 addresses to the whole group, addresses that "clearly identified the names" of each recipient. Three of the accounts had been deactivated, so 15 people actually received it. A recall attempt failed.
Here is the part most coverage misses. The ICO did not just fault the officer for forgetting BCC. It found the force had "inappropriately relied on the use of BCC" for sensitive messages at all. Its email and security guidance says the same: "While BCC can be a useful function, it's not enough on its own to properly protect people's personal information." For anyone on the receiving end, that means your address, and the fact you are on a list, can be the sensitive data.
What Should Organisations Do Now?
The ICO's trends page restates the rule: organisations "are required to report breaches within 72 hours of discovery under Article 33." It also notes that when a reporter gives a date but no time, case handlers record midnight, which "may mean that some breaches are labelled as being submitted outside the 72 hour window" even when they were on time. Always record the discovery time.
- Retire BCC for sensitive mailings. The ICO guidance says organisations should consider "bulk email services or mail merge services" instead, and send individually when there are only a few recipients.
- Configure the mail client. The same guidance recommends rules that "warn email senders when they use the CC field," a send delay "allowing time for you to correct errors," and turning off address autocomplete. The Met had a send delay available but not applied as a group policy.
- Add data loss prevention for outbound mail. Flag messages with many external recipients in To or CC, or with attachments containing identifiers, before they leave the tenant.
- Harden logins against phishing. Move privileged and remote access accounts to phishing resistant MFA such as FIDO2 security keys or passkeys, and follow the NCSC's MFA guidance for corporate services. Our report on passkey phishing against Microsoft 365 covers where even passkeys can be bypassed.
- Write a playbook for both breach types. A misdirected email needs the same 72 hour assessment as a ransomware note: who received it, what it revealed, and whether the risk to people triggers a report.
Individuals have fewer levers, but a few work. If you receive a group email that exposes other recipients, do not reply all, tell the sender, and delete it. If a breach notice reaches you, change the affected password and watch for phishing that cites the leaked details. The NCSC's Jonathon Ellison put the wider point plainly: "many successful cyber attacks still exploit known and preventable weaknesses."
What to Watch Next
The Q4 2026 release will decide whether 2026 overtakes 2023 as the worst year in the ICO's dataset, as The Record expects. Watch two numbers alongside the headline: whether the ICO splits extortion out of "other cyber incidents," and whether its investigation rate moves above roughly 1 in 76. The ICO itself cautions that its figures cover only incidents "discovered and then reported," and that its split between cyber and other incidents "is currently under review." Until it lands, assume both attacks and email mistakes are undercounted.