# UK NCSC Fridge Controller Operation: What Businesses Should Check Now

> What the UK fridge and freezer controller scare means for any business with remotely managed refrigeration, and how to check and close internet exposure today.

Source: https://www.epifive.com/blog/ncsc-commercial-fridge-controllers-what-to-check · Published 2026-11-20 · EpiFive

## Key takeaways

- Pen Test Partners reported on 20 November 2026 that UK supermarkets and suppliers took exposed RDM refrigeration controllers offline after a flaw was found by Omega Solutions.
- The shared lesson across the UK, French and Belgian incidents is that refrigeration controllers should not be reachable from the public internet.
- Firmware updates help but are not a complete fix; removing public exposure and using a VPN or private network for remote access is the stronger step.
- Keep manual temperature logs and alarms working so food safety does not depend on a remote dashboard.

On 20 November 2026 Pen Test Partners published an account of how UK supermarkets and food suppliers quietly took exposed commercial refrigeration controllers offline after a flaw was found in controllers made by RDM. The wider backdrop is a run of attacks on internet-connected fridge and freezer controllers in France and across Europe. If your business has refrigeration that someone can manage remotely, the single most important action is to find out whether any controller is reachable from the public internet and, if so, take it off.

## Who this is for and what you will have

This is for owners and managers of anything that keeps food or medicine cold: restaurants, cafes, grocers, cold stores, caterers, food manufacturers, and the IT or facilities staff who support them. You do not need security expertise. By the end you will have a short list of controllers, a way to find out how each is connected, a set of first actions, and a food-safety fallback so a shutdown of remote access does not become a spoiled-stock problem.

This article does not contain exploit details. None are published by the researchers either, and none are needed to protect yourself.

## What happened

The facts below are attributed to the source that reported them. Sources disagree on some details, and that is noted.

### The UK operation

Pen Test Partners (PTP) says Neil McCourt of Omega Solutions found a vulnerability in RDM refrigeration controllers and contacted PTP in early November 2026. PTP's Andrew Tierney validated the findings and found several additional vulnerabilities. According to PTP, Omega also alerted the NCSC, PTP met the NCSC in person, and the NCSC issued an urgent alert to UK supermarkets through its channels. PTP lists Defra and the Food Standards Agency as taking part in the effort to contact supermarkets and supply chains, but does not describe their specific actions. PTP says retailers and suppliers then worked evenings and weekends to take exposed controllers offline.

Other outlets describe this as a secret national operation affecting thousands of controllers and tens of thousands of refrigeration units. We could not find a page on ncsc.gov.uk describing the operation, so treat the scale as reported by the press, not confirmed by the NCSC. Also note that outlets disagree on who first reported the flaw to the authorities and how the work was organized; this article follows PTP's own timeline.

### RDM's position

RDM issued advisory RDM-SA-2026-001 on 2 November 2026, revised on 3 November. PTP criticized the first advisory as weak: it did not explain what an attacker could do, offer independent validation of the fix, or credit the researcher. PTP also says that after direct engagement RDM's chief executive and chief technology officer were responsive, worked around the clock on new firmware, and contacted operators of controllers it could identify. PTP says the new firmware should fix this issue and several others. Press coverage quotes RDM as saying it detected no malicious activity on its controllers and that exploiting the devices would have required physical hardware. PTP, by contrast, advises treating internet removal as the best option. Both positions are reported here; you do not need to decide between them to act.

### The European attacks

The Record reported that attacks hit supermarket and grocery refrigeration controls across Europe in the early hours of a Monday, likely 2 November 2026, the second wave after an earlier wave in France. Named victims in the UK were three meat suppliers who belong to the Association of Independent Meat Suppliers, and a fruit and vegetable wholesaler. The affected controllers reported there were Copeland XWEB supervisory controllers running firmware version 1.12.1 or earlier, with a fix available since August. The Record says no stock was lost at the meat suppliers, and at the wholesaler a manager unplugged a fridge from the internet after seeing it remotely set to defrost.

The Record also reports that no group has claimed the attacks and UK authorities have not attributed them. NCSC director of operations Paul Chichester said the impact was "minimal" so far, and NCSC chief technology officer Ollie Whitehouse said staff were surprised such systems remain internet-connected in 2026.

### Danfoss controllers

Separately, The Hacker News reported that Dutch consultancy Midnight Blue found six flaws in the Danfoss AK-SM800A controller, five of them in web request handlers that need no login. It reports that no fix was available, no CVE identifiers were assigned, and that Danfoss's advisory page listed nothing for the six flaws at the time. It also says no link between these flaws and the earlier tampering incidents has been established. Treat the Danfoss status as fast-moving and check the vendor's own advisory page.

PTP describes the RDM weakness as related to, but not identical to, the Danfoss weakness. These are different products and different flaws that share one lesson.

## Am I affected?

You are potentially affected if all three are true: you have commercial refrigeration or cold-room controllers, a contractor or vendor can reach them remotely, and that path is not strictly private.

| Situation | Risk | What to do |
|---|---|---|
| Controller reached through a router port forward | High: the controller's login page is visible from the internet | Remove the forward, use a VPN |
| Controller on a cellular modem with a public address | High: easy to overlook, PTP specifically warns about this | Move to a private APN or VPN |
| Vendor cloud portal only, no inbound ports | Lower for the controller itself; depends on the vendor's account security | Strong unique passwords, MFA if offered, review users |
| No remote access at all | Lowest | Keep it that way; still update firmware |
| Contractor says "we manage it" and you do not know how | Unknown | Ask in writing, see below |

Products named in reporting so far are RDM controllers, Copeland XWEB supervisory controllers and the Danfoss AK-SM800A. Absence of a product from that list does not make a controller safe; the same exposure question applies to any brand and to building controllers such as HVAC.

## What to do now

1. **Ask your refrigeration contractor for an inventory.** Request in writing: every controller or supervisory unit on your sites, its make, model and firmware version, and how each is reached remotely (port forward, cellular modem, vendor portal, VPN).
2. **Check your own network edge.** Look in the router or firewall admin page for port forwarding or NAT rules that point to controller addresses. Remove any you cannot justify. Check whether any controller connects through a separate cellular modem or router that your IT team does not manage.
3. **Take exposed controllers off the public internet.** Disconnect remote access if you must, then restore it only through a VPN or protected private network. PTP also advises using a VPN or private APN for cellular modems. The Hacker News summary of the Belgian guidance says allowing only your service company's IP addresses is a short-term measure, not a fix.
4. **Install the vendor's current firmware** for your model, from the vendor's own site or through your contractor. Firmware is necessary but PTP and the agencies cited above say it is not sufficient alone.
5. **Change default and shared passwords** and remove accounts for people who no longer service the site.
6. **Check for tampering.** According to The Hacker News summary of the Belgian guidance, check setpoints, defrost schedules, alarms, user accounts and remote-access settings for changes nobody on your team made.
7. **Protect food safety while you change things.** Manual temperature logs, independent battery-powered temperature loggers with alarms, and a call tree for out-of-hours alerts mean a remote dashboard going dark is an inconvenience and not a loss. In the UK, staff at affected sites were reportedly told to monitor temperatures by hand while controllers were offline; the same approach is sensible anywhere.
8. **Review contracts before cutting data to the service company.** The Hacker News notes that you should check contract and insurance terms and set up protected remote access so monitoring continues.

### If you suspect compromise

Change every credential on the controller and any connected portal, verify connected equipment works properly, keep a record of what you saw (screenshots, times), and report it.

## Who to report to

- **UK:** the NCSC runs an incident reporting service at report.ncsc.gov.uk.
- **US:** CISA's reporting form is reached from cisa.gov/report.
- **India:** CERT-In is the national agency. Use its own site for the current method.
- Also tell your refrigeration contractor, your insurer, and your local food-safety authority if stock may have been affected.

## How to prevent it

- Keep operational technology off the public internet by default. Anything that must be reachable goes behind a VPN or private network with named accounts. Our post on [zero trust remote access](https://www.epifive.com/blog/zero-trust-enterprise-remote-access-architecture) explains the architecture.
- Treat the cellular modem or router at a site as part of your attack surface. Our [office router checklist](https://www.epifive.com/blog/router-firmware-update-change-default-password-office) covers changing defaults, firmware and turning off remote management.
- Put controllers on their own network segment, separate from point-of-sale and office devices.
- Keep a list of every connected device that can change a temperature, and review it every quarter.
- Ask contractors for a security statement when you renew service agreements: how remote access works, who has accounts, and how firmware is delivered. The [FTC small-business cybersecurity basics](https://www.epifive.com/blog/ftc-cybersecurity-basics-small-business) is a useful companion checklist.

## See also

- [Hijacked GitHub Accounts Ran a CI Secret Stealer: Check Your Repos Now](https://www.epifive.com/blog/github-wfx-loot-ci-secret-stealer-check)
- [Google GTIG: AI Agents Exploit Patches, What to Check and Do Now](https://www.epifive.com/blog/google-gtig-ai-agent-exploits-patch-check)
- [Security Defaults vs Conditional Access: Which One Fits Your Small Business](https://www.epifive.com/blog/security-defaults-vs-conditional-access-small-business)
- [SonicWall Gen 6 Firewalls Get No More Patches: What to Do Now](https://www.epifive.com/blog/sonicwall-gen-6-end-of-support-what-to-do)

## What we checked

- Opened the Pen Test Partners post "The fridge hack UK supermarkets narrowly avoided?" on 2026-11-20 and took the timeline, advisory number RDM-SA-2026-001, researcher credits, the NCSC, Defra and FSA roles and the advice from it.
- Opened The Record's report on the European supermarket fridge attacks on 2026-11-20 and took the Copeland XWEB details, victims and NCSC quotes from it.
- Opened The Hacker News article on six unpatched Danfoss AK-SM800A flaws on 2026-11-20; patch status, absence of CVEs and mitigation advice come from it and may have changed since.
- Cross-checked that RDM, Copeland and Danfoss are different products, and that PTP calls the RDM flaw related to but not identical to the Danfoss one.
- Tried to open ncsc.gov.uk news and the Danfoss cybersecurity best-practice page; the NCSC news listing showed no fridge item and the Danfoss page returned HTTP 403, so the scale of the operation and Danfoss's own wording are reported secondhand.
- Not verified: the number of controllers taken offline, the Danfoss fix status, and CERT-In's current reporting method. Not tested on any controller; this article is guidance drawn from the sources below as of the date checked.

Last tested: 2026-11-20

## References

- [Pen Test Partners: The fridge hack UK supermarkets narrowly avoided?](https://www.pentestpartners.com/security-blog/the-fridge-hack-uk-supermarkets-narrowly-avoided/)
- [The Record: British businesses caught in Europe-wide supermarket fridge attacks](https://therecord.media/british-businesses-caught-in-europe-wide-supermarket-fridge-attacks)
- [The Hacker News: Six unpatched Danfoss refrigeration flaws](https://thehackernews.com/2026/11/six-unpatched-danfoss-refrigeration.html)
- [NCSC: Report a cyber security incident](https://report.ncsc.gov.uk/)
- [CISA: Report a cyber incident](https://www.cisa.gov/report)

## Frequently asked questions

### What did the UK do about vulnerable fridge controllers?

According to Pen Test Partners, retailers and suppliers worked to take exposed RDM refrigeration controllers offline after Omega Solutions reported a flaw and the NCSC alerted UK supermarkets. Defra and the Food Standards Agency are listed as taking part in contacting supermarkets and supply chains. RDM has released firmware that it says addresses the issue.

### How do I know if my refrigeration controller is exposed to the internet?

Ask your refrigeration contractor for a list of every controller with remote access, then check how each one connects: a router port forward, a cellular modem with a public address, or a vendor portal. A controller that answers from outside your network, or sits on a modem with a public address, should be treated as exposed.

### Is updating the firmware enough?

No. Pen Test Partners treats taking controllers off the internet as the best option because firmware alone is not a complete fix. Belgian and Irish agencies, as summarized by The Hacker News, say updating firmware, changing default passwords and enabling a vendor's strict mode do not protect a controller by themselves.

### Who should a business report a fridge controller attack to?

Report to your national cyber agency: the NCSC in the UK or CISA in the US. In India, CERT-In is the national agency; check its own site for the current reporting method. Also tell your refrigeration contractor and, for food safety, your local food authority.

