Hacked Freezers: What the Cold-Chain Attacks Mean and What to Do

Attackers are switching supermarket and blood-bank fridges into defrost from the internet. Here is how to keep your controllers off their list.

Featured image

Most security incidents end with stolen data. This one ends with a freezer reading 50°C and a skip full of spoiled food. Since 11 October 2026, attackers have repeatedly broken into the electronic controllers that run commercial refrigeration in supermarkets, and they have used them to push fridges and freezers into long defrost cycles. The first wave hit several hundred stores in France. A second hit more than a hundred stores across Belgium, Sweden, Ireland, Estonia, the Netherlands and other countries on 2 November. On 3 November, France’s national blood service said three of its blood-storage facilities had been affected through a refrigeration supplier.

On 5 November, the FBI and CISA, together with HHS, USDA and DOT, issued a joint warning to every organisation that relies on refrigeration and cold-chain monitoring. CISA’s message was blunt: “Every organization that depends on refrigeration and monitoring systems should assume it could be a target.”

That covers far more than grocery chains. Pharmacies, hospitals, vaccine stores, dairies, frozen-food makers, restaurants, cold-storage warehouses and e-commerce grocery operations all run the same kind of equipment. This post explains what happened, why it worked, and what to do this week.

TL;DR / Key takeaways

  • What: Attackers are logging into refrigeration management controllers that are reachable from the internet and changing temperature setpoints and defrost schedules. Food is spoiled, equipment is stressed, and some sites have reported fires.
  • Who was hit: Hundreds of supermarkets in France (11–13 October), more than 100 stores in at least six European countries (2 November), two Italian food companies, and three French blood-storage sites. Nobody has claimed the attacks.
  • Which equipment: France’s CERT-FR named Danfoss AK-SM and AK-SC controllers and Copeland / Dixell XWEB systems. Danfoss says most hit units were older, end-of-life models, plus some newer AK-SM 800A units on outdated firmware.
  • How they got in: Not officially confirmed. Reported factors include controllers exposed directly to the internet, default passwords, and known flaws in older firmware.
  • Do first: Find every refrigeration and building-control interface you own, take it off the public internet, change default passwords, and check defrost schedules and setpoints for tampering.

Timeline

Dates come from the sources listed at the end. Store counts differ between outlets, so ranges are given where they disagree.

Date (2026) Event
August Claroty’s Team82 publishes research on flaws in the Danfoss AK-SM 800A and Copeland XWEB Pro, and reports about 2,765 internet-exposed AK-SM 800A interfaces. Danfoss tells customers to move to firmware R4.3.1 or later.
11–12 Oct (overnight) First wave in France. Fridges and freezers at Intermarché, Netto, Coopérative U, Carrefour, Monoprix, E.Leclerc and other chains are put into defrost. Reports put the total at roughly 250 to 700 stores.
12 Oct CERT-FR publishes alert CERTFR-2026-ALE-012 covering Danfoss AK-SM and AK-SC controllers. Danfoss confirms incidents affecting “a limited number of refrigeration management systems”.
12–13 Oct Further attacks, also reaching stores with Dixell controllers. CERT-FR later adds Copeland and Dixell XWEB to its alert.
16 Oct CERT-FR updates its alert and says campaigns are “probably still underway”.
1–2 Nov (overnight) New wave hits stores in Belgium, Luxembourg, Sweden, Ireland, Estonia, the Netherlands, Finland, Portugal and Italy.
2 Nov Italy’s national cyber agency (ACN) issues an alert after a Tuscan catering firm and an Emilia-Romagna frozen-food maker are hit.
3 Nov France’s blood service (EFS) confirms an incident at a refrigeration equipment provider that altered temperature and defrost settings at three blood-storage facilities.
5 Nov FBI, CISA, HHS, USDA and DOT publish a joint warning on hardening industrial refrigeration and cold-chain monitoring systems.

How the attacks work

A supermarket does not have one thermostat per freezer. It has a store controller, a small embedded computer with a web interface that manages every refrigerated case, cold room and compressor in the building. It holds the setpoints, runs defrost cycles, raises alarms and lets the refrigeration contractor monitor and adjust everything remotely. Danfoss’s AK-SM 800-series and Copeland’s XWEB are common examples.

Defrost is a normal function. Evaporator coils ice up, so the controller periodically warms them to clear the ice. The attackers abused exactly that feature. According to reporting by Le Monde, cited by WSB-TV, defrost cycles in France were stretched from one hour to eight hours so that alarms would not fire. Swedish and French stores reported cases reaching 50°C. CERT-FR’s guidance specifically tells operators to check defrost schedules, because a tampered schedule can look like a routine setting.

No exploit is required for that last step. Once someone has an administrator session on the controller, changing setpoints and schedules is just using the product as designed. That is why the access question matters so much.

How did the attackers get access?

No agency has published a confirmed entry point, a CVE or indicators of compromise for this campaign. What is on the record:

The FBI/CISA warning, as reported by BleepingComputer, describes attackers targeting “unpatched or internet-accessible electronic temperature controllers” through authentication bypass flaws, code injection or weak configurations.

Why this is worse than it looks

The losses are real. Les Mousquetaires, the group behind Intermarché and Netto, expects losses of “tens of millions of euros”. A single butcher’s shop in Belgium lost about €15,000 of meat. The US agencies also warn of shorter equipment life, fire hazards and unsafe storage conditions.

The bigger risk is silent spoilage. A freezer that obviously fails gets emptied. A cold room that drifts a few degrees above safe limits overnight and then recovers may never be noticed, and that matters most for vaccines, insulin, blood products and chilled food. In one Estonian store the freezer warmed by only two to three degrees before staff fixed it within about ten minutes. Not every site will be that lucky or that alert.

Am I affected?

You are in scope if you operate any of the following and someone, including a contractor, can reach it over a network:

Start with three questions for your facilities team and your refrigeration contractor:

  1. Can the controller’s web page be opened from outside our network? If anyone can reach it with just a browser and an IP address, that is the problem.
  2. Has the default password ever been changed? Check every account, including the “service” or installer account.
  3. What model and firmware is it running, and is it still supported? Danfoss’s AK-SM 800 and AK-SC 355 no longer get updates.

To check exposure from the outside, look up your own public IP ranges in an internet scanning service such as Shodan or Censys and search for web interfaces on those addresses. Internally, the queries below can help. Adjust field names to your logging platform. They assume you already collect firewall logs, and they are starting points, not campaign IOCs (none have been published).

~|-|~|-| Splunk / SQL~|-|style idea: inbound connections from the internet
~|-|~|-| to the subnet or hosts where refrigeration/BMS controllers live.
index~|=|firewall action~|=|allowed direction~|=|inbound
  dest_ip IN ("10.20.30.0/24")        /* your OT / controller subnet */
  NOT src_ip IN ("10.0.0.0/8","172.16.0.0/12","192.168.0.0/16")
| stats count values(dest_port) as ports min(_time) as first max(_time) as last by src_ip dest_ip
| sort ~|-| count
// Microsoft Sentinel (CommonSecurityLog): public sources reaching controller IPs
let ControllerIPs ~|=| dynamic(["10.20.30.10","10.20.30.11"]);  // replace with your controllers
CommonSecurityLog
| where TimeGenerated > ago(30d)
| where DestinationIP in (ControllerIPs)
| where not(ipv4_is_private(SourceIP))
| summarize Hits~|=|count(), Ports~|=|make_set(DestinationPort), First~|=|min(TimeGenerated), Last~|=|max(TimeGenerated) by SourceIP, DestinationIP
| order by Hits desc

Any hit from an unknown public address is worth investigating. On the controllers themselves, review the audit or event log if the model has one, list all user accounts, and compare current setpoints and defrost schedules with what your contractor says they should be.

What to do: a prioritised checklist

Immediately (today)

This week

Longer term

What this means for Pakistan and South Asia

Pakistan’s pharmaceutical distributors, hospital pharmacies, vaccine programmes, dairy and frozen-food producers, and fast-growing grocery delivery businesses all depend on cold chains. In a hot climate, a few hours of forced defrost costs more and is harder to recover from. The equipment is the same as in Europe, and so is the habit of letting an installer expose a controller on a public IP “so we can fix it remotely”. Nothing about this campaign is specific to Europe. Any exposed controller with a default password is a target, wherever it is.

OffensioX perspective

This campaign is a clear sign that attackers have found a cheap way to cause real-world disruption: no ransomware, no zero-day, no ransom note, just a browser and a forgotten login page. Nobody has claimed it, and investigators in Belgium have said the people behind it may never be identified. Whether the motive is sabotage, testing or simple vandalism, the lesson for defenders is the same. Operational technology, such as fridges, HVAC, cameras and building controls, usually sits outside the IT team’s inventory and outside its patch cycle, and it is often managed by a contractor nobody has audited. The first step is not expensive. Find out what you own, find out what the internet can see, and close it.

OffensioX helps organisations map their external attack surface, including OT and building systems, and run penetration tests and security assessments that find exposed controllers before attackers do.

References