National Cybersecurity
Association of Ukraine

Refrigeration as critical infrastructure: what an operator should do.

For operators of warehouses, hospital pharmacies, manufacturing and logistics, and for anyone responsible for equipment that holds a temperature. A refrigeration unit is rarely treated as a cybersecurity asset, until it turns out its controller is reachable from the internet and that the contents of a store can be ruined remotely, without anyone entering the site.

Who this is for and when to use it

This guide covers industrial refrigeration and cold chain monitoring: electronic temperature controllers, control panels, automatic temperature logging, defrost cycle management and energy optimisation.

It matters most where the equipment stands behind health rather than stock: hospital pharmacies, vaccine and blood product stores, pharmaceutical manufacturing and transport. There a spoiled batch is not a line on a balance sheet but a treatment schedule that slips.

Why this counts as critical infrastructure

On 5 November 2026 CISA, together with the FBI, Health and Human Services, the US Department of Agriculture and the Department of Transportation, issued a joint fact sheet on malicious activity against industrial refrigeration and cold chain monitoring systems worldwide 1.

The sectors it names include healthcare and public health, chemical, food and agriculture, and transportation 1. This is not one industry's problem: it is a class of equipment that sits in a supermarket and in a hospital alike.

What is targeted, and to what effect

The agencies describe the targets as electronic temperature controllers and commercial refrigeration controllers, particularly unpatched or internet-accessible ones 1. The main vectors are authentication bypass, arbitrary code injection and weak configurations 1.

The consequences are stated concretely. With access, an attacker can alter settings remotely and force units into continuous heating and defrost cycles. That causes inventory loss, shortens the service life of the system and creates a fire hazard, and product consumed after unsafe storage puts consumers at risk 1.

One listed effect is easy to underrate: loss of visibility into current temperatures. The system appears to run, staff see plausible numbers, and the actual regime is already different. The spoiled batch surfaces after it has shipped.

Why this is not a theoretical conversation in Ukraine

Ukraine already has a documented case of malware reaching into a thermal process rather than an office network. In January 2024 a cyberattack on the Lviv utility Lvivteploenergo temporarily left more than 600 households without heating and hot water 2.

The tool researchers named FrostyGoop spoke to industrial controllers directly over Modbus, a long-standing industrial protocol with no built-in security. Commands were sent to ENCO controllers governing district heating substation modules, producing inaccurate measurements and malfunctions 2. Researchers did not attribute the activity to a specific actor 2.

For this guide the actor is beside the point. The mechanism is what matters: control of a physical temperature process through an ageing industrial protocol turned out to be reachable from a distance. A refrigeration unit is built on the same principle.

Eight actions that close most of the risk

What follows is the mitigation list from the joint fact sheet, in brief. All of it is configuration rather than procurement 1.

  1. 01Take control devices, above all controller panels, off the public internet. Where remote access is needed, put it behind a firewall or edge device and keep that updated.
  2. 02Separate operational technology onto its own network: a dedicated OT VLAN, apart from the business network.
  3. 03Change default passwords, enforce a password policy, and use phishing-resistant multi-factor authentication wherever feasible.
  4. 04Keep firmware current and run lifecycle management: equipment past end of life and no longer supported has to be identified and replaced.
  5. 05Restrict access with device and IP allowlisting, so only authorised addresses can change settings at all.
  6. 06Keep backups offsite and offline, and test them by restoring.
  7. 07Enable logging and review it. Where logs are absent or non-standard, collect network traffic between the assets instead.
  8. 08Define sensible setpoint limits for devices downstream of the controllers so the regime cannot leave a safe range, and alert on deviations.

The last item is the one most often skipped and the cheapest to apply. Bound the setpoint range and a remote instruction to heat continuously simply cannot execute, even when everything else has failed.

Limits of this guide

  • The joint fact sheet names no specific incident, victim, actor or numbered vulnerability. It describes a class of activity, and that is what is summarised here.
  • The Lviv case concerns district heating, not the cold chain. It is cited as confirmed mechanics of interference with a temperature process, not as the same incident.
  • This list is a minimum, not a full industrial security programme. Sites where a loss of cooling threatens life need their own assessment.

Sources

  1. 1CISA, with the FBI, Health and Human Services, the US Department of Agriculture and the Department of Transportation. US Government Partners Urge Hardening Industrial Refrigeration and Cold Chain Monitoring Systems (fact sheet, 5 November 2026) · accessed 2026-11-18
  2. 2The Record, Recorded Future News. FrostyGoop malware left 600 Ukrainian households without heat this winter (23 July 2024) · accessed 2026-11-18