France Blames Shahid Kaveh for Danfoss Fridge Attacks
On November 9, 2026, France formally blamed an Iranian Revolutionary Guard (IRGC) cyber unit for the overnight sabotage of refrigeration controllers at roughly 700 retail sites. This article separates what French authorities and vendors have confirmed from what is still unproven, and lists what defenders who own or manage similar equipment should do.
What happened
Overnight on October 11–12, 2026, attackers reached remote refrigeration controllers across France and pushed them into defrost mode. BleepingComputer reports that the Danfoss controllers' defrost settings were changed to high temperatures. Other outlets report units reaching about 50°C and staying there for roughly six hours, forcing stores to discard fresh and frozen stock.
Timeline from public reporting:
- October 12: CERT-FR, the response arm of ANSSI, published alert
CERTFR-2026-ALE-012on numerous compromises of remote refrigeration controllers. It first named Danfoss AK-SM and AK-SC series devices. - October 13: CERT-FR updated the alert to add Copeland XWEB and Dixell XWEB supervisors, and said campaigns were probably still ongoing. The same day, a propaganda outlet called CyberbanNews publicised the attack, according to France's Cyber Crisis Coordination Center (C4).
- October 21: ANSSI director Vincent Strubel told the French Senate the intrusions relied on basic security failures. Public summaries describe equipment exposed directly to the internet, weak passwords and little meaningful protection. He also warned that healthcare uses similar equipment for vaccines and hazardous materials.
- November 1–2: A second wave hit refrigeration systems elsewhere in Europe, including Sweden. Officials have not publicly confirmed a technical link to the October French compromises, and France has attributed only the October attacks.
- November 9: Foreign Minister Jean-Noël Barrot blamed the IRGC, called the incident the first large-scale sabotage cyberattack on French soil, and said Iran's ambassador had been summoned. France plans to push for EU sanctions. Paris prosecutors opened a judicial investigation. Reporting says arrest warrants were requested for the unit's leader and two deputies.
- November 10: NPR reported that Iran denied involvement.
Attribution basis. C4 attributed the attack to the Shahid Kaveh unit of the IRGC. Per reporting on ANSSI's attribution page, the evidence rests on four indicators: infrastructure characteristics, signature tools, a propaganda outlet linked to the unit that relayed the attack, and traces of Persian in the attack infrastructure. CERT-FR also names a second IRGC-affiliated unit, Shahid Shoostari. The French report says the operators worked through front groups posing as hacktivists, including CyberAveng3rs and Cyber Isnaad Front.
Damage figures. The numbers are not uniform. BleepingComputer and Axios say at least 15 fires. Cybernews and the Paris prosecutor's office, as relayed by Cybersecurity News, say around 20. Losses are described as tens of millions of euros, an estimate from a supermarket owner and press reports rather than an audited figure. One security site notes that fire causation has not been independently established in the official record. Treat the fire count as a government statement, not a forensic finding.
Who is affected
Sectors and scale. About 700 of France's roughly 10,000 supermarkets were affected, plus other retail sites such as butcher shops. Named chains include Intermarché and Netto (Groupement Mousquetaires reported about 300 stores), Coopérative U, Carrefour, Monoprix and E.Leclerc. Counts differ between outlets and chains, so treat 700 as the official approximation.
Products named by CERT-FR:
- Danfoss AK-SM series controllers
- Danfoss AK-SC series controllers
- Copeland XWEB systems
- Dixell XWEB systems (Dixell is a Copeland brand)
Danfoss has said most affected equipment was legacy, naming the AK-SM 800 and AK-SC 355. Copeland has acknowledged a vulnerability in a discontinued, end-of-life generation of controllers but, per reporting, has not confirmed compromises in France. The CERT-FR bulletin itself names no vulnerability and no firmware version.
Exposure data. An IPinfo analysis found that most internet-reachable Danfoss controllers it identified in France ran software with known flaws, including hundreds of end-of-life units. It also counted 1,611 XWEB dashboards in 66 countries, with 70 in France. Italy, where Dixell is based, had 467. Exposure is therefore not a French-only problem.
Adjacent sectors. ANSSI says it has worked with hospitals, pharmacies and laboratories to secure their refrigeration. Pharmacies and labs use similar controllers, so any cold-chain operator with remotely managed refrigeration should read this as a warning.
How the attack works
What is confirmed
The attackers reached the web-based management layer of refrigeration supervisors and sent legitimate commands, mainly defrost settings. In the French incident, Strubel's comments as reported describe the attackers using the controllers' own defrost function. No exploit chain, malware or custom payload is described in the sources reviewed.
What is not confirmed
The initial access method is not publicly established. Cato Networks' threat brief says entry methods remain unconfirmed. Several secondary sources note that neither CERT-FR nor Danfoss has tied the compromises to specific CVEs.
Three Danfoss AK-SM 8xxA flaws are publicly documented and are plausible candidates, but they are background hygiene, not a confirmed vector:
- CVE-2025-41450: improper authentication. Claroty's Team82 describes a hidden "code-of-the-day" login that derives a valid password from the device date. Fixed in firmware 4.2 per Danfoss advisory DSA-2025-03-01.
- CVE-2025-41451: OS command injection leading to remote code execution after authentication, CVSS v3 8.7. Fixed in R4.3.1 per DSA-2025-08-01.
- CVE-2025-41452: configuration-control flaw leading to denial of service after authentication. Also fixed in R4.3.1.
CISA covered these in advisory ICSA-25-140-03. For the Copeland side, Team82 reported 23 vulnerabilities in XWEB Pro (CISA advisory ICSA-26-057-10, fixed in firmware 1.13), including CVE-2026-21718, deterministic admin credentials derived from the date, MAC address and hard-coded keys. Team82 also showed it could manipulate temperature values over Modbus. Reporting says a CISA KEV check on October 8 and 14 found none of these CVEs listed, so no government source confirms in-the-wild exploitation of them.
Another unconfirmed possibility is default or weak credentials on exposed interfaces. CERT-FR's advice to change default passwords and enable Strict security mode on Danfoss units is consistent with that, but it is a recommendation, not a finding.
ATT&CK mapping
The mapping below is deliberately limited to behaviour that public reporting supports. The first two items are inferred from exposure, not from published forensics.
- ICS T0883 – Internet Accessible Device: management interfaces reachable from the internet, as stated by CERT-FR.
- ICS T0855 – Unauthorized Command Message: remote defrost commands sent to controllers.
- ICS T0836 – Modify Parameter: defrost schedules and temperature settings changed.
- ICS T0831 – Manipulation of Control: the physical outcome, with refrigeration operating outside safe bounds.
- Enterprise T1190 – Exploit Public-Facing Application / T1078 – Valid Accounts: candidate initial access paths. Neither is confirmed.
IOCs
Public reporting reviewed does not include a verified IOC list such as IPs, hashes or domains. One third-party blog advertises an IOC section, but its contents could not be corroborated against an ANSSI or vendor source. Check the ANSSI/CERT-FR publications directly for any indicators, and treat unsourced IOC lists with caution. The attribution indicators (infrastructure traits, tooling, Persian-language artefacts) are described qualitatively only.
Detection guidance for defenders
Because the attackers appear to have used native controller functions, endpoint telemetry is largely irrelevant. Most of the signal sits in perimeter logs, remote-access gateways and the controllers' own audit logs. Many of these devices keep thin logs, so network-side visibility matters more.
What to look for
- Inbound connections to controller management IPs or ports from anywhere other than your refrigeration contractor's documented addresses.
- Successful logins to controller web interfaces outside maintenance windows, especially overnight. The attack ran at night.
- Changes to defrost schedules, setpoints or alarm thresholds, plus alarm suppression. CERT-FR specifically says to review the full configuration, including defrost schedules.
- Any controller web interface visible in external scans of your IP ranges.
- Unexpected outbound connections from the controller network, and new users or changed passwords on devices.
Example hunting query
Generic KQL against firewall logs, assuming a ControllerIPs watchlist and a ContractorIPs watchlist you maintain:
let ControllerIPs = _GetWatchlist('RefrigerationControllers') | project DestinationIP = tostring(SearchKey);
let ContractorIPs = _GetWatchlist('RefrigContractorIPs') | project SourceIP = tostring(SearchKey);
CommonSecurityLog
| where TimeGenerated > ago(30d)
| where DeviceAction in~ ("allow", "accept", "permitted")
| where DestinationIP in (ControllerIPs)
| where SourceIP !in (ContractorIPs) and not(ipv4_is_private(SourceIP))
| summarize Hits=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), Ports=make_set(DestinationPort) by SourceIP, DestinationIP
| order by Hits desc
This finds public IPs that successfully reached controller interfaces without being on the contractor allow-list, which are candidates for scanning or unauthorised access.
A second, simpler pseudo-query for the controller or OT historian logs: config_change WHERE parameter IN (defrost_*, setpoint_*) AND time BETWEEN 22:00 AND 06:00 AND user NOT IN approved_service_accounts. It finds off-hours changes to defrost or setpoint parameters made by anyone other than approved accounts.
Note that an overnight defrost cycle is normal behaviour. The anomaly in this attack was the setting being held hot, so alert on duration and temperature thresholds, not on the presence of defrost.
Finally, an independent temperature sensor with its own alerting path, not routed through the compromised controller, is the most reliable detection control. Commentary on this incident notes that the missing pieces were visibility into exposure and monitoring that could notice a forced defrost in progress.
Mitigation and response
- Take management interfaces off the public internet now. This is CERT-FR's core instruction. Find every AK-SM, AK-SC, XWEB and Dixell unit, including ones installed by contractors that your IT team does not know about. Check your own external IP ranges, since exposed devices are visible to anyone scanning.
- Restore remote access only through a secure VPN or protected network with authenticated, authorised users. Source-IP allow-listing of contractors is acceptable only as a temporary emergency measure, per CERT-FR. Check insurance contract terms before cutting data feeds to refrigeration contractors, as CERT-FR advises.
- Patch supported units. For Danfoss AK-SM 8xxA, apply firmware R4.3.1 or later, which covers CVE-2025-41451 and CVE-2025-41452. Firmware 4.2 addressed CVE-2025-41450. For Copeland XWEB Pro, apply firmware 1.13 (vendor advisories cite v6.30.2313). For Dixell XWEB, follow Dixell's secure-use recommendations linked from the CERT-FR alert. Patching is not a substitute for removing exposure, as no source confirms these CVEs were the vector.
- Harden configuration. On Danfoss controllers, enable Strict security mode and change all default passwords, as CERT-FR advises. Use unique credentials per site.
- Handle end-of-life units separately. CERT-FR states that a factory reset alone is insufficient for exposed end-of-life equipment, which remains likely to be compromised again. Danfoss's stated route for unsupported controllers is migration to a supported platform. Until replacement, isolate them completely.
- If a controller may be compromised: remove it from the internet, review the whole configuration including defrost schedules, then factory reset, reconfigure and restore access through a secure connection. A reset removes attacker artefacts but also destroys evidence, so capture configuration, logs and network traces first if you may need them for prosecutors or insurers.
- Add out-of-band safety monitoring: independent temperature probes and alerts, and a documented manual-override procedure so staff can act when a controller misbehaves.
Retailers that outsource refrigeration to third parties should ask contractors in writing which controllers are internet-exposed, which firmware they run, and who holds the credentials. Reporting notes that supermarkets commonly outsource refrigeration and may not manage its security directly.
What individuals should do
Shoppers have little to do technically. The practical issue is food safety: if a store reports a refrigeration failure, follow its guidance and do not buy affected chilled or frozen goods. Anyone running a small shop, cold store or lab with a remotely managed refrigeration unit should ask the installer whether its web interface is reachable from the internet, and have it removed if so.
FAQ
Was a zero-day used?
Public reporting does not confirm one. CERT-FR's bulletin names no vulnerability. The publicly documented Danfoss and Copeland flaws were disclosed and patched in 2025 and early 2026, and no source reviewed confirms they were exploited in this attack.
Is the Iran attribution settled?
It is France's official government position, backed by four indicators described in ANSSI's attribution material. Iran denies involvement, and the underlying technical evidence has not been published in full. The November 1–2 wave across Europe has not been attributed.
Is it safe to just factory reset a compromised controller?
For supported, patched, non-exposed units, CERT-FR says a reset removes what the attacker left behind. For exposed end-of-life units, a reset alone leaves them open to re-compromise. Preserve evidence first if you may need it.
Bottom line
The sophistication here was low and the impact was high. Attackers did not need novel malware, only internet-reachable controllers and their own defrost function. State-attributed sabotage of this kind will recur wherever OT management interfaces face the internet. The priority for defenders is an inventory of exposed controllers and a closed perimeter, with firmware updates as a secondary step.
Original reporting: BleepingComputer
Protect yourself with tools recommended by cybersecurity professionals:
The tools below are independently selected based on security audits, transparency, and real-world effectiveness.