NCSC: AI-Powered Ransomware Against UK Critical Infrastructure Is 'Highly Likely' by 2028 — and Old, Tolerated Weaknesses Are the Reason

AI · 2026-11-04 · By H.A

NCSC: AI-Powered Ransomware Against UK Critical Infrastructure Is 'Highly Likely' by 2028 — and Old, Tolerated Weaknesses Are the Reason

The NCSC's State of the Cyber Nation report says criminals are highly likely to use AI-powered malware in ransomware attacks on UK critical national infrastructure by 2028, because AI lets them exploit long-tolerated legacy weaknesses at unprecedented scale.

What Happened

The UK's National Cyber Security Centre (NCSC) published its annual State of the Cyber Nation report on November 3 in London. The headline assessment: by 2028, it is "highly likely" that financially motivated criminals will use AI-powered malware in ransomware attacks on UK critical national infrastructure, such as power stations, airports and hospitals.

NCSC chief executive Richard Horne, launching the report, warned of "a real prospect of an unprecedented rise" in cyber incidents, driven by AI. His central point was not that AI has invented new attacks. It is that weaknesses organisations have tolerated for years can now be found and exploited at a scale that was not possible before.

What the Report Says About AI

The NCSC's argument, in summary:

This builds on Horne's speech in June, when he said around three-quarters of the 200-plus incidents affecting UK critical infrastructure in the year to May 2026 were believed to be linked to state actors. At the time, the NCSC assessed that by 2028 AI-enabled capabilities would likely be used to exploit known vulnerabilities in legacy technology across critical infrastructure. The November report keeps the 2028 horizon and adds the explicit ransomware warning.

The PHP2Shell Example

The NCSC pointed to the recent PHP2Shell vulnerabilities as a preview. These were critical flaws in the PHP language core, and AI helped discover them. The NCSC said it sent about 110,000 proactive notifications and Early Warning alerts to UK organisations about them. That one AI-assisted discovery could require six-figure notification volumes shows the kind of scale the agency is preparing for.

The Failings Horne Called Out

Horne was blunt about why the risk is so high. He criticised:

His message to boards was to use the tools, standards and frameworks that already exist, and to treat security and resilience as a core requirement rather than an add-on.

What the Government Is Funding

The report comes alongside measures the UK government announced in late October, including:

For smaller organisations, Cyber Essentials certification is being discounted by 75%. More than 230 businesses have signed a Cyber Resilience Pledge that lets them refer supply-chain SMEs for free certification. The government has also introduced the Cyber Security and Resilience Bill, with a National Cyber Action Plan to follow.

What To Do Now

The report is aimed at the UK, but its advice applies to any organisation running critical or legacy systems:

  1. Inventory internet-facing legacy systems and assume AI-assisted scanners will find every one of them. Anything end-of-life and exposed should be isolated, replaced or put behind strong access controls.
  2. Shorten the patch window for edge devices and public-facing software. The gap between disclosure and mass exploitation is shrinking.
  3. Enforce least privilege for vendor and remote access, and remove standing access that exists only for convenience.
  4. Monitor what matters: log and alert on OT boundary traffic, remote-access gateways and identity systems.
  5. Govern internal AI deployments: inventory AI agents and tools, limit their permissions, and log their actions like any other privileged account.
  6. Build and rehearse ransomware recovery for operational systems, not just IT, including offline backups and manual fallback procedures.

Why It Matters

Government cyber agencies rarely give a date for a specific kind of attack. The NCSC's "highly likely by 2028" is a formal intelligence assessment, not a vendor prediction, and it puts AI-driven ransomware against hospitals and utilities on a two-year timeline. The diagnosis matters more than the forecast: AI is not the root cause. It accelerates attacks on the unpatched, end-of-life and over-permissioned systems that organisations have chosen to live with. Fixing those was already overdue. The NCSC is saying the time to do it is running out.

COMPUTE NODE · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Run local models, watch a live threat feed, and ship security work.

0threats tracked
0news & posts
0live intel sources
0geo-tagged map
0resolving host

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a browseable threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

News

Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

Loading…

Posts

Loading…

Loading posts…

Forum

Questions, answers, and talk about running AI locally.

Loading forum…

GitHub repositories

Curated AI and security repos, plus your own pinned shelf.

Command board

One-liners, configs, and advice worth keeping — shared by everyone here.

⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
Loading commands…

Skill packs

Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

Loading skills…

Threat Intelligence

Curated threat write-ups, advisories and analysis — with cover media.

Loading…

Tutorials

Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

Loading…

Downloads

Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

Loading…

Terms & Conditions

Loading…

Help & FAQ

Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


Formatting guide

Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

Contact us

Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

Loading…

Send a message

VAPT Report Generator

Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

Recon Toolkit

Passive OSINT lookups for the recon phase of an engagement, plus offline hash identification and a payload cheatsheet.

Website Checker

Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

Control panel

Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

Overview
Content
Site
Account & Security

Email settings

SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

"From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

Send a test email

Sends through whichever provider is currently active above. Save your settings first if you just changed them.