French blood service says a cyberattack on a provider hit its cold-room controls. No blood was lost, and an alarm that did not depend on the provider caught it
On 2 Nov 2026 a cybersecurity incident hit the remote monitoring and control of cold rooms at three sites of the French blood service (EFS), run through a refrigeration provider. Temperatures in the controls were driven far above the freezers' normal setting. The EFS says no health impact and no blood product was lost. What is confirmed, what differs between reports, and what a small company can learn about provider access.
Updated 10 Nov 2026: see what changedHow urgent
Good to know
Who is affected
The French blood service (Établissement français du sang, EFS), at three regional sites whose cold rooms were controlled through a refrigeration provider's remote software; the provider says only a limited number of its units were affected. Any business that lets a provider run or watch its equipment remotely
What to do
Ask every provider that can reach your equipment or accounts remotely: which components in its software come from other companies, how it is updated, and how you would know if it were abused. Turn off remote access you do not use. Keep at least one alarm or monitor that does not depend on that provider, and write down what to do by hand if the provider's system cannot be trusted
Published 5 Nov 2026 · Sources last checked 10 Nov 2026No. 50 / 87
Updates, follow-ups and corrections
- Update · 10 Nov 2026. On 9 Nov 2026 France attributed the October attack on its supermarkets to Iran's Revolutionary Guards (see our story on the supermarket fridge attacks). The report we read about that attribution, from France 24, does not mention the blood service, and we have not seen any authority link the incident at the French blood service to it. Nothing in the statements we read changes what the EFS and its provider said about this incident.
- Update · 6 Nov 2026. On 5 Nov 2026 CISA, the FBI, HHS, USDA and the Department of Transportation published a joint fact sheet urging operators to harden industrial refrigeration and cold-chain monitoring systems, saying they are aware of malicious activity worldwide against electronic temperature controllers and commercial refrigeration controllers that are unpatched or reachable from the internet. It lists authentication bypass, code injection and weak configurations as the ways in, and names no incident, victim, attacker or CVE. Its advice matches ours: take the controllers off the public internet, put them on a separate network, change default passwords, patch or replace unsupported units, set safe temperature limits with alerts, and keep offline backups. We read the fact sheet directly.
- Update · 5 Nov 2026. First version of the story, based on the AFP report published by France 24 and the report by ICI (both 4 Nov 2026, read directly). We did not read the statements of the EFS, of the provider or of the ministry themselves, and the technical cause is not public. Reports differ on the temperatures, as explained below.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On Monday 2 November 2026 a "cybersecurity incident" hit the systems that monitor and control cold rooms of the French blood service (EFS) at three regional sites, according to the EFS as reported by AFP. The rooms hold blood samples and plasma bags used for transfusions and to make medicines. The first report came from the weekly *Le Canard enchaîné*, which said the attack targeted Coolworld, a refrigeration provider to the EFS. The EFS and the health minister's office confirmed the incident.
Coolworld says it was an incident on its remote monitoring software, that the weakness came from "a component supplied by a third-party provider", and that only a limited number of its units were affected.
What the EFS says
The EFS says no health impact has been identified and no blood product was lost. A duty technician noticed the problem, and it was handled with monitoring systems that do not depend on the provider. The minister's office lists the measures: remote access to the equipment was cut, monitoring was reinforced and products were moved to other facilities. Technical investigations continue into how it was done, how many devices were affected and when the equipment will be back in service. A new update is promised.
The temperatures: reports differ
*Le Canard enchaîné*, as relayed by AFP, says rooms that keep samples at -30 °C were programmed to reach 110 °C. ICI quotes an EFS manager, Christophe Barisien, saying temperatures climbed "to 110 or even 150 degrees", that the sensors raised the alarm and that samples were not altered. ICI also says the Besançon site, the only affected site in Bourgogne-Franche-Comté, keeps products at -25 °C. We report these figures as the sources give them. We cannot say which is exact, and AFP notes that the 110 °C figure is a programmed setting reported by the newspaper.
What we could and could not confirm
We read the AFP report (France 24) and ICI directly. We did not read the original statements, we do not know who is behind the attack or how they got in, and AFP says a link with the recent supermarket-fridge attacks across Europe is not established. We do not claim one.
Why it matters if you are not a blood service
The lesson is about provider access. The way in was not the EFS's own network but a remote monitoring tool run by a provider, built with a component from yet another company. The same pattern appeared this week with a bank, where attackers used a service provider's platform. And what limited the damage was an independent alarm and a person on duty.
What to do
- List the providers that can reach your equipment, accounts or data remotely (hosting, monitoring, payments, support tools).
- Ask each one which third-party components its remote software uses and how it is updated.
- Turn off remote access you do not use, and use separate credentials for each provider.
- Keep at least one alarm or monitor that does not depend on that provider, and make sure someone gets the alert.
- Write a short manual fallback: what you do if you cannot trust the provider's system for a day.
If you build with AI tools
Our advice, not from the sources: AI-built projects often add a monitoring or support tool with remote access in a few lines. Ask your assistant which third-party components that tool pulls in, what permissions it has, and whether you have an alarm that does not depend on it.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- France 24 (AFP): "Des chambres froides de l'Établissement français du sang victimes d'une cyberattaque d'un prestataire", 4 Nov 2026 (read directly) (opens in a new tab)
- ICI: "Cyberattaque : des chambres froides de l'Établissement français du sang victimes d'un piratage informatique", 4 Nov 2026 (read directly) (opens in a new tab)
- CISA, FBI, HHS, USDA and DOT: US Government Partners Urge Hardening Industrial Refrigeration and Cold Chain Monitoring Systems (fact sheet, 5 Nov 2026, official, read directly) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.