Overnight into Monday 12 October 2026, hackers seized control of the connected refrigeration systems of several hundred French supermarkets and forced fridges and freezers up to 50 degrees Celsius, spoiling fresh and frozen food on a massive scale, sparking fires in some stores and causing losses that already run into the millions of euros. The Paris prosecutor’s office has opened an investigation into what it described as a large-scale cyberattack, Prime Minister Sébastien Lecornu has tasked France’s cybersecurity agency ANSSI with the technical inquiry, and the Danish software vendor whose refrigeration management systems were targeted says the affected units were running outdated firmware. Because the incident sits at the crossroads of cybercrime, food safety, product liability and cross-border investigation, it is a textbook case for explaining how French law actually responds when an invisible intrusion suddenly becomes very physical: hot air blasting from freezer cabinets on Monday morning, entire aisles condemned, and two supermarkets in Alsace alone reporting combined losses of 270,000 euros according to broadcaster BFMTV.
For an international reader — a supplier, an insurer, a consumer passing through France, or counsel advising a retailer with French stores — the questions are concrete. Which French criminal charges fit an attack that heats fridges instead of encrypting servers? What must a supermarket chain do with tonnes of possibly unsafe food? Who pays when the flaw sits in a vendor’s software? And how do French investigators pursue hackers who may have acted from abroad, while a Dutch retail giant reports a possibly related security incident on the same day? This analysis answers each question from verified sources: the exact texts of the French Criminal Code as in force on 12 October 2026, three recent rulings of the criminal chamber of the Cour de cassation quoted word for word, and the statements made on the record by the chains, the vendor and the authorities as reported by Reuters, the BBC and AFP.
I. French supermarket fridges hacked to 50°C: which criminal charges apply in France?
The facts as reported are unusually tangible for a cyberattack. According to Reuters, hackers forced the temperature of many French supermarket fridges up to 50 degrees Celsius overnight, and the Paris prosecutor’s office confirmed reported damage including food losses and fires. The BBC reported that Intermarché told Reuters its fridges had heated to 50 degrees for six hours overnight into Monday and that the retailer threw all the affected food away to avoid health risks, while staff in some stores were hit by waves of hot air when they opened freezer units on Monday morning. Les Mousquetaires, the group that owns Intermarché, said through a spokesperson that around 150 of its stores had been hit. Coopérative U chief executive Dominique Schelcher said several of his chain’s supermarkets had been struck by what he called an extremely serious and unprecedented attack, writing on X that targeting equipment essential to preserving fresh products and supplying food to the French people was a matter of extreme gravity without precedent. AFP, cited by the BBC, reported more than 100 Coopérative U supermarkets targeted and at least 300 Intermarché and Netto stores affected, while specialist and local media mentioned possible impacts at other major chains, which had not confirmed anything at the time of reporting. Numbers still vary because the full scale remains unclear, and every figure below should be read with that reservation: only the judicial investigation will establish the final count.
A. Hacking, blocking and altering automated systems: what Articles 323-1 to 323-3 punish
French criminal law does not need a special supermarket statute to capture this attack. Chapter III of Book III of the Criminal Code punishes attacks on automated data processing systems, and each technical step of the fridge incident maps onto a distinct offence. The starting point is fraudulent access and fraudulent continued presence in such a system. Article 323-1 of the Criminal Code provides: “Le fait d’accéder ou de se maintenir, frauduleusement, dans tout ou partie d’un système de traitement automatisé de données est puni de trois ans d’emprisonnement et de 100 000 € d’amende.” The same article raises the penalty where the intrusion had consequences: Article 323-1 continues, “Lorsqu’il en est résulté soit la suppression ou la modification de données contenues dans le système, soit une altération du fonctionnement de ce système, la peine est de cinq ans d’emprisonnement et de 150 000 € d’amende.” A refrigeration controller whose temperature set points were rewritten overnight from chilled to 50 degrees is, on the facts as reported, precisely a system whose operation was altered, so the aggravated five-year bracket is the natural starting hypothesis for prosecutors, subject to proof of each element at trial.
Two recent rulings of the criminal chamber of the Cour de cassation show how broadly French courts read this offence, and both matter here. On 2 September 2025 (appeal no. 24-83.605, ECLI:FR:CCASS:2025:CR00934, rejection), the Court upheld the conviction of a network administrator who had kept consulting his manager’s emails, holding: “se rend coupable de l’infraction prévue par l’article 323-1 du code pénal celui qui se maintient dans un système de traitement automatisé de données en prenant connaissance du contenu des messages échangés au sein du réseau, à des fins étrangères à sa mission et à l’insu des titulaires des messages, même si, administrateur du réseau, il bénéficie, de par ses fonctions, d’un droit général d’accès à la messagerie.” The lesson for the fridge case is direct: if the investigation were to find that the attackers entered through legitimate remote-maintenance accounts of the refrigeration vendor or a service provider and then acted for purposes foreign to that mission, the existence of an initial access right would not, in itself, defeat a charge under Article 323-1. Earlier, on 16 January 2018 (appeal no. 16-87.168, ECLI:FR:CCASS:2018:CR03366, rejection), the Court had already stated: “se rend coupable de l’infraction prévue à l’article 323-1 du code pénal la personne qui, sachant qu’elle n’y est pas autorisée, accède, à l’insu des victimes, à un système de traitement automatisé de données ; D’où il suit que le moyen ne saurait être accueilli ;” Knowledge of the lack of authorisation plus secrecy toward the victims is therefore the core of the offence, and an overnight mass temperature change imposed on hundreds of stores without any warning fits that core uncomfortably well for whoever ordered it.
Beyond mere access, the attack as described instantiates two further offences. Article 323-2 punishes obstruction of the operation of an automated data processing system: Article 323-2 states, “Le fait d’entraver ou de fausser le fonctionnement d’un système de traitement automatisé de données est puni de cinq ans d’emprisonnement et de 150 000 € d’amende.” Forcing controllers to heat instead of cool for six hours is arguably the textbook falsification of a system’s operation, distinct from the initial intrusion. Article 323-3 then covers the manipulation of the data itself: Article 323-3 provides, “Le fait d’introduire frauduleusement des données dans un système de traitement automatisé, d’extraire, de détenir, de reproduire, de transmettre, de supprimer ou de modifier frauduleusement les données qu’il contient est puni de cinq ans d’emprisonnement et de 150 000 € d’amende.” Each rewritten temperature set point, each falsified sensor reading displayed on a cabinet, each altered log could support this qualification alongside the other two, because French cybercrime charges are routinely combined rather than treated as alternatives.
Three aggravating and ancillary provisions complete the prosecutorial toolkit. First, the tooling offence: Article 323-3-1 targets “Le fait, sans motif légitime, notamment de recherche ou de sécurité informatique, d’importer, de détenir, d’offrir, de céder ou de mettre à disposition un équipement, un instrument, un programme informatique ou toute donnée conçus ou spécialement adaptés pour commettre une ou plusieurs des infractions prévues par les articles 323-1 à 323-3”, punishable by the same penalties as the underlying offences. In the 16 January 2018 ruling cited above, the courts added that this legitimate-purpose exception is narrow: the Bordeaux appeal court, upheld on this point, held that the authorisation to hold such equipment is limited to persons qualified to maintain and secure a computer network, and that motives such as defending one’s professional situation are irrelevant to the characterisation of the offence. Anyone found holding the exploit kit tailored to the refrigeration controllers would therefore face an uphill argument. Second, organised crime: Article 323-4-1 provides, “Lorsque les infractions prévues aux articles 323-1 à 323-3-1 ont été commises en bande organisée, la peine est portée à dix ans d’emprisonnement et à 300 000 € d’amende.” A coordinated overnight strike on hundreds of stores across France, possibly from abroad and possibly synchronized with incidents in neighbouring countries, is exactly the kind of factual pattern in which investigators will test the organised-gang hypothesis, including through telephone and financial analysis. Third, attempt is fully punishable: Article 323-7 states, “La tentative des délits prévus par les articles 323-1 à 323-3-1 est punie des mêmes peines.” Failed intrusion attempts against chains that repelled the attack would therefore remain prosecutable on their own.
On the investigative side, the Paris prosecutor’s decision to open the case centrally is consistent with how digital evidence is gathered in France. Article 56 of the Code of Criminal Procedure authorises the seizure, where proof of the crime may be obtained that way, of “papiers, documents, données informatiques ou autres objets”, and the 16 January 2018 ruling confirmed that home searches aimed at computer data seized under this article need no separate authorisation beyond the framework of the preliminary inquiry. Controller logs, vendor remote-access records, firmware images and the compromised set-point histories of hundreds of stores can thus be preserved and seized quickly, before overwriting or remote wiping destroys them — a decisive practical point when the crime scene is a distributed fleet of connected fridges rather than a single server room.
B. Fires, spoiled food and millions in losses: property damage and food safety offences
The cyberattack did not stay in the digital realm: the Paris prosecutor’s office itself reported fires among the damage, and Reuters described fires alongside food losses at several hundred stores. Where an intrusion causes fire damage to another person’s property, French law adds a heavyweight qualification. Article 322-6 of the Criminal Code provides: “La destruction, la dégradation ou la détérioration d’un bien appartenant à autrui par l’effet d’une substance explosive, d’un incendie ou de tout autre moyen de nature à créer un danger pour les personnes est punie de dix ans d’emprisonnement et de 150 000 euros d’amende.” Ten years’ imprisonment is the same tariff as the organised-gang cybercrime bracket, and it applies per fire-damaged store wherever the causal chain from the remote manipulation to the blaze is established by expert evidence. Even where no fire broke out, the tonnes of food rendered unfit and the overheated equipment itself fall under ordinary property damage: Article 322-1 punishes “La destruction, la dégradation ou la détérioration d’un bien appartenant à autrui” with two years’ imprisonment and a 30,000 euro fine, except for merely minor damage — an exception plainly inapplicable to losses already estimated in the millions, with two Alsace stores alone reporting 270,000 euros of damage according to BFMTV.
Food safety is the second front, and here the retailers’ own conduct becomes legally relevant. Intermarché told Reuters it threw all the affected food away to avoid any sanitary risk, and that destruction decision is precisely what European and French food law expects when the cold chain breaks so spectacularly. Under Article 19 of Regulation (EC) No 178/2002, food business operators that consider or have reason to believe that food they have placed on the market may be injurious to health must withdraw it and, where it may already have reached consumers, recall it and inform the competent authorities. A freezer cabinet displaying 26.5 degrees in an ice-cream aisle, as shown in the BFMTV image, or units heated to 50 degrees for six hours, leaves no room for doubt about the break in the cold chain, so systematic destruction with traceability, rather than any attempt to salvage stock, is the only defensible course — and the public confirmation of that destruction also protects the chains against later accusations of having resold unsafe goods. The official French full text of the regulation is available on EUR-Lex at Regulation (EC) No 178/2002.
French case law underlines how strictly courts treat cold-chain and hygiene management systems once harm is alleged. On 31 March 2020 (appeal no. 19-82.171, ECLI:FR:CCASS:2020:CR00606, rejection), the criminal chamber upheld convictions for involuntary injury in a contaminated minced-meat case, endorsing the appeal judges’ analysis: “Ils précisent que l’agrément délivré par la direction départementale de la cohésion sociale et de la protection des populations suppose que le professionnel a mis en place des contrôles de conformité des produits qu’il réceptionne et qu’il fabrique en établissant un plan de maîtrise sanitaire (PMS) qui doit obligatoirement prendre en compte le risque lié à la contamination par la bactérie E-Coli et par la bactérie E-Coli 0157H7 et être approuvé par l’administration.” The context was bacterial contamination, not hacking, but the principle travels: approval to handle food presupposes a validated sanitary control plan, and a retailer that can show immediate quarantine, documented destruction and notification to the authorities places itself on the right side of that principle. Conversely, any store that, through disorganisation in the chaos of Monday morning, allowed warmed products to remain on sale would face a much darker analysis, because the regulatory framework treats the operator, not the hacker, as the guarantor of what sits on the shelves. Consumers in France can check the official recall portal at RappelConso, although in this case destruction before sale should normally make consumer recalls unnecessary.
One reservation must be stated clearly, because no accident, intrusion or damage beyond what the official and press sources report should be assumed. At the date of writing, no injury to any person has been reported by the authorities, no responsibility has been judicially established against any identified perpetrator, and the contracts signed between the chains, their refrigeration service providers and the software vendor will ultimately govern the allocation of the financial loss between them. Only the courts will decide the final qualifications. The criminal analysis above describes the charges the facts as reported could support, not convictions, and every participant remains presumed innocent.
II. Supermarket cyberattack in France: who pays, who fixes the software and who investigates across borders?
Once the immediate emergency — cutting power to overheated cabinets, ventilating stores, destroying unsafe stock — is over, three longer battles begin: allocating millions in losses between retailers, service companies and the software vendor; securing every remaining connected fridge in France and Europe; and finding perpetrators who may never have set foot in France. Each battle has its own French and European legal framework, and the statements already on the record shape all three. Danfoss, the Danish company whose refrigeration management software ANSSI identified as the vulnerable vector according to a source close to the Prime Minister cited by Reuters, said it was aware of incidents in France affecting a limited number of refrigeration management systems, that the affected units were running outdated firmware, and that it had long advised customers to keep supported systems updated and to migrate legacy systems to current generations. On the same day, Dutch group Ahold Delhaize disclosed a security issue in its own network, took several systems offline, and reported its online app and delivery systems down with electronic price tags displaying wrong information in the Netherlands and Belgium, while Luxembourg and Belgian Delhaize stores were also affected according to Belgian media — with Reuters stressing that no link with the French attack had been established. European Commissioner for food Christophe Hansen condemned the hack on X, declaring that food security requires more attention at all levels because, in his words, the weaponisation of food has become a reality.
A. Spoiled food worth millions: vendor liability, outdated firmware and insurance
The first question every affected store owner will ask is who bears the cost of the destroyed stock, the damaged equipment, the business interruption and the emergency response. Between the parties, the signed contracts come first: maintenance agreements for the refrigeration fleet, software licences and update clauses, remote-monitoring contracts and cyber-insurance policies will each allocate risks, response duties and caps, and only a clause-by-clause review can say whether a missed firmware update was the retailer’s breach, the service provider’s breach or a shared failure. But beneath the contracts sits a mandatory layer of French tort law that no clause can simply erase as against third parties. Article 1245 of the Civil Code lays down the principle: “Le producteur est responsable du dommage causé par un défaut de son produit, qu’il soit ou non lié par un contrat avec la victime.” And Article 1245-3 defines the defect functionally: “Un produit est défectueux au sens du présent chapitre lorsqu’il n’offre pas la sécurité à laquelle on peut légitimement s’attendre.” A refrigeration management system that allows a remote actor to impose 50 degrees on food cabinets for six hours, with fires as a reported consequence, would have serious difficulty meeting the safety a user can legitimately expect — although the vendor’s statement that only outdated firmware was affected opens the classic defence that the defect, if any, lies in the failure to update rather than in the product as placed on the market, a question that turns on the presentation of the product, its reasonably expected use and the time it was put into circulation, all of which Article 1245-3 requires courts to weigh.
European product law reinforces this analysis for software. The new Product Liability Directive (EU) 2024/2853 expressly brings software within the notion of product and updates the rules on defect, burden of proof and the development-risk defence, with Member States required to transpose it — its official text is on EUR-Lex at Directive (EU) 2024/2853. Parallel to liability for the past, the Cyber Resilience Act, Regulation (EU) 2024/2847, imposes forward-looking duties on manufacturers of products with digital elements, including vulnerability handling, security updates and coordinated disclosure, available at Regulation (EU) 2024/2847. For connected equipment as sensitive as food refrigeration, these instruments converge on one practical message that retailers and their counsel should carry into every negotiation with vendors: remote update mechanisms, supported firmware windows and documented end-of-life migration paths are no longer commercial options but the baseline of legal compliance, and Danfoss’s own emphasis on updating supported systems and migrating legacy ones points in exactly that direction.
Network and data regulation adds a second layer of duties for the chains themselves. If the compromised refrigeration platforms processed personal data — loyalty data, staff access logs, or customer information transiting through connected store systems — the General Data Protection Regulation requires notification of the supervisory authority within 72 hours of awareness where the breach is likely to create a risk, and communication to the affected individuals where the risk is high, under Articles 33 and 34 of Regulation (EU) 2016/679, with France’s CNIL (CNIL) as the competent authority for the French stores. Separately, the NIS2 Directive (EU) 2022/2555, available at Directive (EU) 2022/2555, brings food production, processing and distribution entities within its personal scope as important entities and subjects significant incidents to staged reporting to the national CSIRT — in France, ANSSI (ANSSI) — alongside risk-management and supply-chain security measures whose national transposition retailers must now track closely. Whether each individual supermarket company crosses the directive’s size thresholds, and whether this incident qualifies as significant for each of them, will need case-by-case assessment, but groups the size of Intermarché, Coopérative U or Ahold Delhaize are precisely the operators the directive was written for. Cyber-insurance policies, finally, will be tested on every classic battlefield at once: the definition of the insured event, the adequacy of the declared security measures including patching discipline, waiting periods for business interruption, and subrogation actions against the vendor — which is why preserving the firmware images, the update history and the access logs identified above matters as much for the civil recovery as for the criminal case.
B. From Paris to Amsterdam: how France prosecutes a cross-border refrigeration hack
The investigation opened by the Paris prosecutor’s office will immediately face the question every major French cyber case raises: where are the perpetrators, and how does France reach them? French criminal law applies to offences committed on French territory, including where the harmful result occurs in France even if the keystrokes happened abroad, so hackers who heated fridges in France from servers elsewhere remain prosecutable by French courts once identified. The Prime Minister’s office added two significant details reported by Reuters: France is coordinating with its European counterparts because other countries may also be affected, and ANSSI was formally tasked with the technical investigation. That coordination has a ready-made legal home. France is a party to the Budapest Convention on Cybercrime (CETS No. 185, Council of Europe Treaty No. 185), which provides expedited preservation of stored data across borders, mutual assistance for real-time collection and a 24/7 contact network designed for exactly this scenario: volatile logs held by a Danish vendor, transit data in a third country, suspects logging in from a fourth. Within the European Union, the European Investigation Order (Directive 2014/41, Directive 2014/41/EU) allows French magistrates to obtain evidence located in another Member State — hear the vendor’s engineers in Denmark, seize server images in the Netherlands — through a single standardised order subject to recognition, while Eurojust and Europol can support a joint investigation team if the Dutch, Belgian and French strands turn out to share one perpetrator.
That conditional is essential, because the Dutch angle must be handled with full prudence. Ahold Delhaize described only a security issue and said its Albert Heijn stores in the Netherlands and Belgium remained open; Reuters explicitly noted it was unclear whether any link existed with the French attack. A responsible analysis therefore treats the two incidents as separate until the investigators say otherwise, while noting the operational hypothesis any cyber prosecutor would test: a shared software supply chain. The source close to the Prime Minister said ANSSI had identified a vulnerability in software supplied by Danish company Danfoss, and Danfoss confirmed awareness of incidents in France affecting a limited number of refrigeration management systems. If the same vendor’s systems equip stores in several countries, then the same unpatched vulnerability could explain simultaneous symptoms without any coordination between attackers — or, conversely, a single actor could have exploited one flaw across borders. Distinguishing those scenarios is the technical core of the coming months: firmware version inventories across fleets, comparison of intrusion artefacts, and timeline correlation between the French overnight heating and the Dutch systems taken offline. What can already be said is that the cross-border dimension strengthens rather than weakens the French case: European coordination mechanisms exist precisely so that evidence does not evaporate while letters rogatory travel.
For victims and witnesses, the procedural roadmap is straightforward. Retailers and their insurers should file criminal complaints with constitution de partie civile so that they gain access to the case file and can claim damages within the criminal proceedings; the 2 September 2025 ruling recalled that moral damages for breach of the trust placed in a custodian of a system are compensable, the Court approving 10,000 euros for facts committed, in its words, “au mépris de la confiance” placed by the victim with directly caused, certain and significant harm. Consumers who may have bought warmed products before destruction should keep receipts and packaging, check RappelConso, and consult a doctor at the slightest symptom, since the limitation periods for any personal-injury claim run from the appearance of the harm. Suppliers whose goods were destroyed in the condemned aisles should notify their own insurers and preserve delivery records, because the allocation of the loss between retailer, service provider and vendor will be fought document by document.
Conclusion
The October 2026 refrigeration cyberattack will be remembered as the night French cybercrime law met the cold chain. On the facts reported by Reuters, the BBC and AFP — hundreds of stores heated to 50 degrees for hours, fires, millions in destroyed food, a vendor vulnerability identified by ANSSI and a simultaneous security incident at a Dutch group whose connection remains unproven — French law already offers a complete response without waiting for any new statute: Articles 323-1 to 323-3-1 and 323-4-1 of the Criminal Code for the intrusion, the obstruction, the data tampering and any organised dimension, with attempt punishable identically; Article 322-6 where fire damage is established and Article 322-1 for the destroyed stock and equipment; the withdrawal and destruction duties of food law, validated by courts that treat sanitary control plans as the price of the right to sell food; the no-fault product liability of Articles 1245 and following of the Civil Code for defective software, now backed by the European product liability and cyber-resilience instruments; and the full cross-border machinery of the Budapest Convention, the European Investigation Order and ANSSI-led European coordination to reach perpetrators wherever they typed. Retailers that destroyed every doubtful product, preserved every log and filed prompt complaints will have done everything the law expects of victims; vendors that document supported update paths and migrate legacy systems will have done everything it expects of manufacturers; and investigators who correlate the French, Dutch and Belgian artefacts before the data fades will have done everything it expects of them. The courts will have the last word on qualifications and responsibilities, but the direction of travel is already clear: connected equipment that guards what a nation eats is critical infrastructure in fact, and the law is rapidly treating it as such.