On this page (7 sections)

On November 9, 2026, French authorities publicly blamed Iran for an October cyberattack that remotely took over refrigeration control systems in hundreds of French supermarkets and drove temperatures far above safe levels. Paris prosecutors tie the operation to units of Iran's Islamic Revolutionary Guard Corps (IRGC), summoned Iran's ambassador, and are seeking international arrest warrants.

This is a sabotage story rather than a software vulnerability story, and no CVE or vendor advisory has been published for it in the material we reviewed. It still matters to anyone who runs websites, stores or hosting, because the same weakness class (internet-reachable control systems and the accounts that manage them) shows up in business networks of every size.

What happened

According to SecurityWeek (AP), attackers remotely took control of refrigeration systems in hundreds of supermarkets and independent stores in the early hours of October 12. Temperatures climbed to 50 Celsius (122 Fahrenheit) for about six hours, forcing stores to throw away fresh and frozen goods. The Intermarché chain reported losses of "tens of millions of euros" in a single day.

On Monday, November 9, Paris prosecutor Laure Beccuau said a formal judicial investigation had been opened into suspected organized cybercrime, with the aggravating circumstance of acting in the interests of a foreign power. Foreign Minister Jean-Noel Barrot described it as the first large-scale cyberattack aimed at sabotage on French soil and said it would not go unanswered.

How France reached its attribution

Infosecurity Magazine reports that investigators from the Anti-Criminality Office (OFAC) and the domestic intelligence service (DGSI) found IP addresses linked to Iran-based endpoints and Farsi words in traces left by the attackers. They also said the tactics, techniques and procedures matched earlier Shahid Kaveh campaigns. A CERT-FR technical notice published on November 9 links Shahid Kaveh to several purported hacktivist personas, including CyberAveng3rs, Soldiers of Solomon, Mr. Soul and Cyber Isnaad Front, and names three IRGC leaders.

Treat the attribution as a government assessment. Language and IP traces can be planted, which is why investigators also cite behavior patterns, but the underlying evidence has not been published. The two articles we used are also not fully independent: SecurityWeek's piece is Associated Press reporting, and both rely largely on the same prosecutor and agency statements.

The sources differ slightly on the second group. Infosecurity Magazine says the investigation found links to both Shahid Kaveh and Shahid Shoostari for this attack. SecurityWeek says ANSSI attributed this attack to Shahid Kaveh and tied Shahid Shoostari to other attacks since 2020, such as the 2023 Charlie Hebdo operation and the 2024 Paris Olympics organizers.

What is still unknown

The reporting does not say how the attackers got in. It does not name the refrigeration controller vendor or product, any vulnerability that was used, or whether credentials, exposed management interfaces or a service provider were involved. No CVE is cited. Anyone claiming a specific technical cause at this point is speculating, and this article does not.

Related incidents are also not fully established. SecurityWeek reports that a cyberattack on several French blood banks tried to raise temperatures to extremely high levels but was thwarted before damaging blood products. Infosecurity Magazine notes that the attack on the French Blood Service in early November is not part of this attribution. SecurityWeek also says supermarkets in Sweden, Belgium, Luxembourg, Ireland and Estonia had freezer and fridge problems the previous week that "apparently" were caused by cyberattacks. That link is not confirmed in the sources.

Who is realistically exposed

Most readers do not run supermarket refrigeration. But the pattern applies broadly: remotely managed equipment such as cold-storage controllers, building management systems, cameras, HVAC, point-of-sale hardware and kiosks, often installed by a third party and then forgotten. If you run a store, restaurant, warehouse, clinic or office, or host systems for clients who do, ask who can reach these devices from the internet and which accounts can change their settings.

Because the entry method is unknown, the steps below are general hardening practices, not a fix for a specific flaw.

What to do now

  1. List every connected device that controls physical processes (refrigeration, HVAC, access control, cameras) and note who installed, manages and can remotely reach each one.
  2. Remove direct internet exposure. Put management interfaces behind a VPN or a vendor-managed secure gateway with multi-factor authentication.
  3. Change default and shared passwords, and give vendor and installer accounts individual logins that you can disable.
  4. Segment these devices from office, payment and web server networks so one compromise cannot spread.
  5. Ask each vendor or service provider for current firmware versions and a security contact, and apply updates in a planned maintenance window.
  6. Set independent temperature alarms and local manual override or failsafe procedures, so a remote takeover does not depend on the same system being attacked.
  7. Keep logs of remote access and configuration changes, and review them for logins at unusual hours or from unexpected countries.
  8. Write a short runbook: who to call, how to isolate a controller, and how to protect stock or data if control is lost.
Caution. Do not disconnect or reconfigure live refrigeration or medical-storage controllers without a fallback plan and the vendor's guidance. A hasty change can cause the same spoilage you are trying to prevent.

Detection and monitoring

Physical sensors and alarms are your best early warning for this kind of attack, since a six-hour temperature climb is visible long before the loss is complete. On the IT side, watch for changes in what is exposed to the internet. An outside-in scan of the sites and hosts you own, such as Webforta Scan, can show which services are reachable from outside, and Webforta Monitor can alert on certificate, DNS and header changes. Neither tells you that a specific controller is safe, so treat them as one layer next to device-level controls.

For wider context on protecting a small business, see our small business website security guide. If you suspect a compromise, follow Website hacked: what to do.

What happens next

France says it will urge European partners to adopt additional sanctions against Iranian individuals and entities, and it reserves the right to take further public and undisclosed measures. It is not yet clear what form the sanctions will take. Watch for the CERT-FR technical notice and any vendor or ANSSI guidance, which may finally name the entry method and give defenders indicators to check.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. France Blames Iran for Supermarket Fridge Hackinfosecurity-magazine.com ·
  2. France Blames Iran for a Cyberattack That Heated Supermarket Refrigeratorssecurityweek.com ·
  • Iran
  • France
  • OT security
  • Sabotage
  • Attribution
  • IoT