Attackers spent the night heating French supermarket freezers on purpose.

Hundreds of stores lost chilled and frozen stock after someone reached refrigeration controls and cooked the inventory. That is the cybersecurity problem sitting in your buildings right now. Ahold Delhaize shops in the Netherlands and Belgium spent the same cycle on an unspecified store “security issue.” You can run polished threat detection on laptops and still miss the compressor VLAN.

Cold rooms sit on live networks

Facilities still treat refrigeration as a vendor box in a back room. It is a networked controller with a maintenance path, leftover default credentials, and a business impact measured in pallets.

French reporting described freezers behaving like ovens. Product destroyed. That is a safety and loss event your incident response runbook probably parks under “building systems” until food-safety staff are already dumping aisles.

If a contractor can change setpoints from a laptop, so can whoever steals that session. Remote HVAC and refrigeration portals are the same privileged path you already fight on jump hosts. They often skip the firewall policy you put in front of POS. They skip MFA. They ride cellular or a quiet VLAN nobody named in the last audit.

Your cold chain is an endpoint.

Ahold Delhaize’s disruption across Dutch and Belgian stores is the twin lesson. A stalled register floor stops a grocer as surely as melted stock. A store-level security event that freezes labels, logistics, or checkout has the same public shape: closed aisles and angry queues.

Defense in depth for retail starts where temperature lives. Store Wi-Fi, corporate laptops, and the BMS should not share a broadcast domain. They often do, because the fridge “isn’t IT.”

A gateway from a refrigeration vendor, a decade of “temporary” remote access, and a store manager who cannot tell you the IP of the panel that keeps ice cream solid.

Outages hit the plant and the docs

This was an availability week for operators who still budget as if leaks are the only headline.

Canonical’s Ubuntu site, blog, and developer portal ate a second DDoS this year. If you were pulling a package note or an install guide while something else burned, you felt it. Public docs are production for every shop that ships from that tree.

Ukraine then knocked a third Yandex data center offline with drones. Payments, deliveries, and other digital services across Russia stumbled because a building lost power and chillers.

The cloud is a room with a roof.

Grocery refrigeration, a Linux project’s websites, a search company’s plant. Different actors. Same operator job. Keep the process that runs the business reachable only by people you can name, and recoverable when that bet fails. Corporate threat-protection will not cool a walk-in.

Cybersecurity starts at the compressor

You do not need a new platform to stop this class of loss. You need an owner, a network drawing, and a weekend of security hardening on systems facilities still calls “the fridge guy’s box.”

Do the immediate work before the next maintenance window gets hijacked.

• Inventory every refrigeration controller, BMS panel, gateway, and vendor remote-access tool in stores, DCs, and commissaries. Name the firmware, the path to the internet, and the human who can change a setpoint.
• Put those hosts behind deny-by-default firewall policy. No direct inbound from store Wi-Fi, guest networks, or corporate user VLANs. Egress only to named vendor addresses if you must keep remote support.
• Disable unused remote maintenance. Force MFA and a jump host for whatever remains. Kill shared passwords on HMIs. Treat brute-force against those portals as a store-down event, not background noise.
• Wire temperature, door, and compressor alarms into the same incident response channel that gets ransomware pages. A sudden climb toward ambient is a security signal.

Ongoing cyber security work is dull and it works. Re-verify segmentation after every remodel. Tabletop the moment a freezer trend goes the wrong way: who calls food safety, who pulls the vendor, who snapshots the controller, who talks to the press. Edge threat-protection that only watches POS will not see a BACnet write.

Map the protocols the panel speaks. If you cannot see those writes in a log you control, you cannot investigate a setpoint change after product is already warm.

Keep last-known-good setpoints in the machine room. Staff should take a controller off-net and hold temperature without a vendor NOC in another country.

Keep vendor cellular modems off unless you are watching them. A silent 4G stick on a rack is an unauthenticated WAN port in a store you thought was local-only.

Practice the fail-safe. If the controller lies, can staff hold temperature with a local override, or did you centralize so hard that a bad session cooks a region?

The fridge VLAN is hostile until you prove otherwise.

French grocers paid in thawed pallets. You will pay in the same currency if refrigeration is still a facilities mystery. Put it on the asset list. Then put it behind a door your SOC can actually see.

Sources

• Cyberattacks hit European grocers: French supermarket freezers hijacked, Dutch and Belgian stores disrupted
• Canonical Websites Disrupted in Second DDoS Attack This Year
• Ukraine strikes third Yandex data center, disrupting digital services across Russia