When cyberattacks become physical: lessons from the supermarket refrigeration attacks
In October 2026, hundreds of supermarket refrigeration systems in France were reportedly compromised by cyberattacks. On 2 November, a second wave affected retailers across several European countries.
Attackers gained access to refrigeration control systems and manipulated their operating parameters, forcing some refrigerators and freezers into defrost mode. In some cases, temperatures reportedly reached 50°C.
The consequences? Spoiled food, financial losses and disruption to supermarket operations.
What caused the attacks?
The attacks targeted remote refrigeration controllers, including Danfoss AK-SM and AK-SC series and Copeland and Dixell XWEB systems.
These controllers manage refrigeration operations and can be remotely accessed by maintenance companies. The French cybersecurity agency CERT-FR warned that exposing their management interfaces directly to the Internet creates a significant security risk.
There are two particularly concerning aspects:
- Outdated equipment and firmware: some affected controllers were end-of-life products or running outdated firmware, leaving known security weaknesses unaddressed.
- Insecure remote access: in the November attacks in the Netherlands, Danfoss confirmed that some affected installations were still using factory-default passwords and were not protected by secure networks.
The exact initial access method used in the attacks has not been publicly confirmed. Previous vulnerabilities identified in Danfoss controllers should not automatically be considered the vulnerabilities exploited in these incidents.
When cyberattacks become physical risks
This incident demonstrates how a cyberattack on a connected product can quickly become a physical, operational and economic problem.
The consequences are not limited to spoiled food and financial losses. Similar attacks could disrupt medical devices, industrial automation, automotive systems, building management and energy infrastructure.
When connected products are compromised, the impact can extend far beyond cybersecurity.
Why does the Cyber Resilience Act matter?
The European Cyber Resilience Act (CRA) makes cybersecurity a product lifecycle responsibility.
Manufacturers must understand the components of their products, identify and assess security risks, manage vulnerabilities and implement appropriate mitigations. These activities cannot be limited to product development or initial certification: they must continue throughout the product's lifecycle.
Understand your attack surface
Identify and manage potential threats associated with product characteristics, including:
- Unauthorized access and authentication bypass.
- Remote code execution and command injection.
- Exposure of management interfaces.
- Network-based attacks and denial of service.
- Firmware manipulation and unauthorized updates.
- Privilege escalation.
- Manipulation of sensors, actuators and control parameters.
Manufacturers must also define, track and verify security mitigations, establishing:
- Which mitigations are required.
- Who is responsible for implementing them.
- Who is responsible for verifying their status and evidence of implementation.
This creates clear accountability and makes security measures part of an ongoing product security process.
Know the components in your products
Securing a connected product starts with understanding what is inside it. Identify the hardware and software components inside your product, including controllers, microprocessors, communication modules, memory and third-party software.
Understand what can go wrong
Continuously monitor vulnerabilities affecting product components, assess their applicability and exploitability, identify relevant mitigations and prioritize remediation.
The objective is to connect vulnerabilities to actual product characteristics and the conditions required for exploitation.
How could Product Security Management have helped?
The incidents highlight two distinct categories of security risks:
Both could have been addressed as part of Product Security Management.
- Identify components: use HBOM and SBOM to maintain visibility of hardware and software components and identify known vulnerabilities.
- Define product threats: identify potential attack scenarios based on product characteristics, interfaces and capabilities.
- Track security mitigations: define required security measures, assign responsibility for their implementation and verification, and maintain evidence of their effectiveness.
- Continuously monitor vulnerabilities: identify newly disclosed vulnerabilities, assess their applicability and exploitability, and prioritize remediation.
This approach helps manufacturers identify security weaknesses earlier, establish clear responsibilities and maintain control over product security throughout its lifecycle.
Sources
- CERT-FR – Security alert CERTFR-2026-ALE-012 (12 October 2026)
- The Hacker News – Attackers Heat French Supermarket Fridges Up to 50°C (13 October 2026)
- NL Times – Refrigeration systems of 17 Dutch businesses attacked (2 November 2026)