Refrigeration Controller Security: 6 IoT Lessons From France
Refrigeration controller security sounds like a niche topic until a few hundred supermarkets start warming up overnight.
According to the Tech Startups roundup of October 12, 2026, hackers disrupted refrigeration controls at roughly 150 to 300 French stores overnight on October 11 and 12, pushing temperatures as high as 50ยฐC. Older Danfoss controllers were reportedly the main targets, with similar disruptions in the Netherlands and Belgium. I could not confirm the details from a second independent source at the time of writing, so treat the scale as reported, not final.
What we can say with confidence is that this class of attack has been predicted by researchers for a while.
Why refrigeration controller security is an IoT problem
A supermarket cooler is no longer a dumb box. It has a networked controller that logs temperatures, sends alerts and often exposes a web interface so technicians can manage it remotely. That is classic industrial IoT: useful, cheap to run, and frequently forgotten once installed.
Security researchers at Claroty’s Team82 documented exactly this risk. In their published research on Danfoss controllers, they described three flaws in the AK-SM 800A web interface that chain together: an authentication bypass using a date-based “code of the day” (CVE-2025-41450), command injection leading to remote code execution (CVE-2025-41451) and a configuration injection that can crash the management interface (CVE-2025-41452). They found about 2,765 of these interfaces exposed to the internet. The fix is firmware R4.3.1 or later, though Danfoss’s own advisory should confirm which version covers each CVE.
To be clear, that research does not prove these specific flaws were used in France. It shows why attackers would find these devices attractive.
Lesson 1: Never expose a management interface to the internet
This is the single biggest fix. A controller reachable from anywhere is a controller that will be scanned within hours. Put management access behind a VPN or a restricted management network, and check with an external scan that nothing is listening on the public side.
Lesson 2: Know every connected device you own
Many retailers cannot list all their networked controllers, let alone their firmware versions. Start an asset inventory: device type, location, owner, firmware, and how it connects. You cannot patch what you do not know exists.
Lesson 3: Old hardware needs a plan, not hope
Older controllers are the reported targets. If a device no longer receives updates, isolate it on its own network segment, restrict who can talk to it, and budget for replacement. The CISA industrial control systems guidance offers practical segmentation advice.
Lesson 4: Segment operational and corporate networks
Cooling controllers should never share a flat network with point-of-sale or office laptops. A compromise in one place must not become a compromise everywhere. Segmentation is boring, cheap relative to a spoiled stock room, and extremely effective.
Lesson 5: Monitor temperature and logins together
Most stores watch temperature alone. Add login monitoring and change alerts for the controller’s configuration. A sudden setpoint change at 2 a.m. plus a login from an unknown address is a story you want to hear in minutes, not at opening time.
Lesson 6: Test your manual fallback
Can staff move stock and read temperatures manually if the network is down? Run a drill. The NIST Cybersecurity Framework treats response and recovery as equal partners to prevention for a reason.
What this means for Pakistan and South Asia
Cold chains matter here too: vaccines, dairy, pharmaceuticals and the fast-growing cold storage sector all depend on connected controllers. Many installations use imported devices with default settings and no named owner for security. Yeh risk kal ka nahi, aaj ka hai.
If you run or build IoT systems, add security reviews to the delivery checklist: no default passwords, signed firmware updates, no public management ports, and a documented patch process.
Key Takeaways
- Treat controllers as computers: They run web servers and need patching like any other server.
- Reported does not mean confirmed: The French incident details come from a single roundup, while the underlying vulnerability research is well documented.
- Remove internet exposure first: VPN or restricted access beats any other single control.
- Inventory, segment, monitor: These three habits catch most real-world problems.
- Practise the manual fallback: Recovery plans only work if people have rehearsed them.
How TecniForge Can Help
At TecniForge, we help businesses navigate these technology shifts. Whether you need custom software development, AI integration, or cloud migration, our team builds scalable solutions with security in mind from the first design review. Talk to our experts.
Do you know how many internet-facing devices your business runs right now, and who is responsible for patching each one?
Discover more from TecniForge
Subscribe to get the latest posts sent to your email.