Goldilock
English
EnglishDeutschFrançaisEspañolPolskiTürkçeالعربيةNederlandsItaliano

Refrigeration controller security

The 2026 attacks did not need exotic tools. They needed a controller that could be reached from the internet. Here is how to make sure yours cannot.

Updated

Supervisory refrigeration controllers run a store’s or warehouse’s cases, cold rooms and compressor racks. They hold set points, schedule defrost, raise alarms and log temperatures for food-safety and pharma records. Most have a web interface and a network port so that a refrigeration contractor can monitor and adjust them remotely.

That remote access is what attackers used in 2026. Reporting on the European attacks named Danfoss AK-SM and AK-SC units and Copeland/Dixell XWEB controllers among those targeted. Any make can be at risk if it is reachable from the internet.

What attackers change

  • Set points. Raising a frozen case from −18 °C to +50 °C turns the refrigeration into a heater.
  • Defrost schedules. Forcing defrost stops cooling and looks like routine maintenance at first glance.
  • Alarm thresholds. Widening alarm limits delays the moment anyone notices. At the French blood service, both temperature and defrost thresholds were pushed to extreme values.

A controller security checklist

Work through these in order. The early steps cost little and close the most common paths.

  1. Find every controller. List each supervisory unit, gateway, modem and remote-access box across every site, including ones your refrigeration contractor installed and manages.
  2. Check what is reachable from outside. Confirm none has a public IP address or open port-forward. Ask each vendor exactly how they connect.
  3. Update firmware and change default passwords. Apply vendor fixes, including those in CISA advisory ICSA-25-140-03 for Danfoss AK-SM 8xxA units.
  4. Put vendor access on a timer. Remote service should be opened for a visit and closed afterwards, not left on permanently.
  5. Keep an independent temperature alarm. A separate monitoring path that an attacker on the controller cannot silence is how EFS caught its attack early.
  6. Physically isolate what does not need to be online. A FireBreak port per controller makes it unreachable outside the windows you choose, and lets you cut everything off at once during an incident.
  7. Write down the manual fallback. Know how to run each plant locally and where product goes if a cold room fails.

Why physical isolation fits refrigeration

Refrigeration controllers are unusual in OT: they must run continuously, but they rarely need to talk to anyone. A controller that is offline still holds its set points. That makes them ideal candidates for a layer 1 disconnect that stays open most of the day and closes only for data uploads or service.

Find out which of your controllers an attacker can reach

We map every refrigeration controller, gateway and vendor connection across your sites, show you which ones are reachable, and design where FireBreak ports go. You get the map whether or not you buy hardware.

Book an exposure check