Five US agencies published a joint fact sheet on 5 November 2026 on hardening industrial refrigeration and cold chain monitoring systems (full text in the IC3 copy). If you operate electronic temperature or commercial refrigeration controllers in retail grocery or cold storage, run refrigerated transport, or monitor temperatures in a health and medical supply chain, it is addressed to you, as is ENISA's joint statement of 4 November. Neither describes a new technique. What is new is that the mitigations now come in a stated order.

If you run refrigeration or cold chain monitoring controllers

CISA, the FBI, HHS, the USDA and the Department of Transportation state they "are aware of malicious cyber activity targeting industrial refrigeration and cold chain monitoring systems globally" (fact sheet, as of 5 November 2026, read 16 November 2026). In scope are operators of these controllers in retail grocery and cold storage, across the Healthcare and Public Health, Chemical, Food and Agriculture and Transportation Systems sectors. Their first three steps, in order: do not expose control system devices, particularly controller panels, to the internet, and where remote access is necessary protect it with a firewall or edge device updated to the latest version; create a dedicated OT VLAN separating OT devices from business networks; then change default passwords, strengthen passwords under a policy, and use phishing-resistant multifactor authentication wherever feasible.

What the statements say, and what they leave out

The fact sheet is careful about tense: the agencies are aware of actors targeting these controllers, and the routes it describes are possibilities. Actors "may exploit vulnerabilities or weaknesses in unpatched or internet-accessible controllers to remotely alter settings and force units into continuous heating and defrost cycles," through authentication bypass, arbitrary code injection and weak configurations. Listed effects include a fire hazard, loss of inventory, and loss of visibility into temperatures, a denial-of-view condition.

ENISA's statement, naming the Commission's DG CNECT, Europol's EC3, the EU CSIRTs Network and EU-CyCLONe with it, reports incidents affecting commercial refrigeration systems and similar devices in a number of Member States since 11 October 2026, with a new wave on 1 and 2 November. It names no product.

Neither names a vendor, model or firmware version. The product names belong to CERT-FR, whose alert CERTFR-2026-ALE-012 reports numerous compromises of Copeland xweb, Danfoss AK-SC and AK-SM series and Dixell xweb remote controllers, and says campaigns are probably still under way. Published 12 October, it was last revised 16 October and still reads that way on 16 November 2026. No CVE appears in any of the three, and nothing for those vendors is in CISA's Known Exploited Vulnerabilities catalog at version 2026.11.13 (KEV feed, read 16 November 2026). We covered the October incidents here.

What this means if you run cold chain monitoring

Read the eight mitigations as an argument rather than a checklist and the ordering works. Exposure sits first because it is the only condition the fact sheet attaches to the activity: unpatched or internet-accessible controllers. Everything below it reduces what an actor can do after arriving. Nothing below it reduces the chance of arrival.

Step seven carries the admission that matters most for monitoring. The agencies ask for logging and regular review, then add that where OT logs are non-standard or unavailable, operators should collect network traffic between the assets. That is a government body conceding that these devices often cannot say what happened to them, and that the network has to answer instead. It is also why denial-of-view is an effect rather than an inconvenience: the monitoring system is both the control and the record an auditor or an insurer later asks for.

What to do if you operate industrial refrigeration or cold chain monitoring

Now

  • The first three steps are in the section above, in the fact sheet's order.
  • CERT-FR's caution comes before any exposure work: check your insurance contract conditions before cutting the data feed to your refrigeration service provider (CERT-FR, revision of 16 October 2026, read 16 November 2026).
  • Scope check, per the fact sheet's overview: identify any of these systems accessible from the internet, remove unnecessary remote access, secure what remains. CISA's Internet Exposure Reduction Guidance (revision date 21 August 2026) adds that the assessment has to include third-party access such as vendor VPNs and cellular modems, and has to be repeated.
  • If you run Copeland xweb, Danfoss AK-SC or AK-SM, or Dixell xweb, CERT-FR publishes two sequences. Uncompromised: remove internet exposure from the unit and from any unit on a public IP address, verify the whole configuration including the defrost schedules, restore access only through a secure VPN or protected network, with source IP filtering an emergency measure and not a lasting one, then the manufacturer's good practice, given for Danfoss as security level Strict and changed default passwords. Compromised: remove the exposure, restart the Danfoss unit or failing that restore factory settings, restore access only by VPN or protected network, reconfigure before returning it to service, then the manufacturer's good practice.
  • Then the remaining mitigations in the fact sheet's order: keep firmware up to date and establish a lifecycle process to identify, retire and replace end-of-life devices [CPG 2.A, 2.B], noting that the BOD 26-04 and BOD 26-02 guidance linked there binds US federal civilian agencies and not you; maintain device and IP address allowlisting so only authorised devices and addresses can make changes [CPG 3.H]; keep current backups offsite and offline, and test them [CPG 3.O]; enable logging and review it, collecting network traffic between assets where OT logs are non-standard or unavailable [CPG 3.Q]; and set setpoint limits downstream of controllers with alerting for deviations.

This week

  • Reporting, if something has happened: the fact sheet gives US organisations the CISA 24/7 Operations Center and the FBI's IC3, with HHS named for impacts on healthcare delivery. EU entities in scope of NIS2 report significant incidents to their national CSIRT or competent authority, per ENISA's statement. The Cyber Resilience Act duty that has applied since 11 September 2026 binds manufacturers rather than operators; that clock is here.
  • Our recommendation: produce the register the allowlisting and lifecycle steps assume, naming per unit the model, the firmware version read off it, whether it holds a public IP address, and who dials in. Where no such list exists, the asset inventory gap is what to close first.

Plan

  • Work the connectivity design against the guidance the fact sheet lists as a resource, the UK NCSC's Secure connectivity principles for operational technology, produced with CISA, the FBI, BSI and four other agencies. Its principles: balance the risks and opportunities; limit the exposure of your connectivity; centralise and standardise network connections; use standardised and secure protocols; harden your OT boundary; limit the impact of compromise; log and monitor all connectivity; establish an isolation plan.
  • Our recommendation: the isolation plan and the manual operation step both assume somebody has written down which zones may reach the refrigeration estate. Segmentation is usually thinner in practice than a network diagram suggests.

If you cannot patch

No advisory we opened names a CVE or a fixed version, so there is no patch to chase. For units past support, the fact sheet's answer is the lifecycle process: identify, retire and replace what the manufacturer no longer supports. CERT-FR adds that keeping an unfixed end-of-life unit exposed to the internet creates a very high probability of compromise, and that a factory reset alone is insufficient, since it removes persistence while leaving the device vulnerable. Danfoss's product security page returned HTTP 403 on 16 November 2026, so no firmware version here is attributed to a vendor.

If you are not affected

The fact sheet's scope is systems used for automated and remote temperature monitoring, continuous logging, defrost cycle management and energy optimisation, and the activity it describes reaches unpatched or internet-accessible controllers. A controller with no internet path, no standing vendor remote access and a dedicated OT VLAN does not meet those conditions, and there may be nothing further to do. Record it as mitigated by configuration rather than not affected, and date a recheck, since CERT-FR still reports campaigns probably under way and a service visit can reinstate remote access.

Where the work comes down to knowing which controllers exist and what they ask the equipment to do, that is what our OT security services and managed OT SOC are for.