Steve Miller's Blog

The Pentagon Is Treating Freezer Malfunctions on Military Bases as a Suspected Hack: Who in Your Organization Owns the Building Systems on Your Network?

Three facilities and IT professionals review building systems plans together at a desk in a modern office.

When a freezer fails, the first call usually goes to facilities, not the security team. That habit is about to get tested. Reuters reported on October 29, 2026 that the Pentagon is treating a string of freezer malfunctions at U.S. military bases as a suspected hack. That puts building management system cybersecurity, and the refrigeration and facility controllers that sit next to it, squarely on the agenda for anyone who runs a network with equipment from a facilities vendor plugged into it. Which is most of us.

What Has Been Reported

According to Reuters, as published by Military Times, the Pentagon is treating “the spate of mysterious freezer malfunctions that spoiled food at military bases across the United States in August as a suspected hack,” according to four officials familiar with the matter. Reuters said it could not establish how far the investigation had progressed or whether it had reached any conclusions about what happened or who was responsible. The Pentagon said a unit of Cyber Command was “working in close coordination with interagency and law enforcement partners.” Army CID said its Cyber Field Office was involved and was working with French law enforcement on “the refrigeration outages in Europe.”

Reuters’ review of the bases’ own Facebook posts and website updates found that the late-August malfunctions affected at least six commissaries, the on-base grocery stores. In at least one case, the freezers did not simply stop. Their temperatures were turned up overnight. Fort Huachuca, Arizona posted that its freezer “went into defrost mode where it heated up all the food.”

Back on September 1, Stars and Stripes reported that Army CID’s Cyber Field Office and the Air Force Office of Special Investigations had confirmed active investigations. Based on each installation’s online announcements, it named the affected stores as Fort Irwin, F.E. Warren Air Force Base, Fort Huachuca, Naval Station Newport, Columbus Air Force Base, and Travis Air Force Base. At that point, the Defense Department would acknowledge only a “possible refrigeration disruption.”

On attribution, Nextgov/FCW reported that U.S. officials suspect Iran-linked hackers, citing two anonymous people familiar with the matter. Nextgov also said it is not clear how the intruders may have accessed the freezer systems, and that the assessments could change. I want to be precise here. As of these reports, no official has publicly confirmed that this was a cyberattack, how it was done, or who did it.

Why the French Parallel Matters

Reuters connects the U.S. investigation to a cyberattack earlier in October on commercial freezers in France. That attack overrode temperature controls at more than 350 establishments and, like Fort Huachuca, involved raising temperatures rather than just shutting units off. Danfoss, whose controllers ran many of the affected French units, said many devices were obsolete or running outdated firmware. Reuters could not establish whether Danfoss or any other controller brand was in use at the U.S. bases.

Bill Moore, CEO of Xona Systems, told Reuters the root problem is that controllers “initially conceived as isolated interfaces that would be serviced by an in-person technician were increasingly being connected to the internet.” That one sentence describes a lot of the building systems I have seen on corporate networks.

The Ownership Gap in Building Management System Cybersecurity

Here is my opinion: building systems fall through organizational cracks. Facilities buys the HVAC controls, refrigeration, access control, and lighting. A vendor installs them, often with remote access for service. IT provides a network port, or the vendor brings a cellular modem. Security never sees an asset inventory. When something goes wrong, the ticket says “equipment failure,” and nobody asks whether someone changed a setpoint on purpose.

The incidents in these reports show why that matters. A freezer that heats up overnight looks exactly like a mechanical fault until someone checks who, or what, changed the configuration.

My Recommendations: Assign the Owner Before the Incident

These are my recommendations, not Defense Department or vendor guidance.

  1. Name a single accountable owner for building and facility systems security. This is a governance decision, not a technical one. Write it down. Facilities can operate the systems, but someone in security must own their risk.
  2. Inventory every controller. HVAC, refrigeration, BMS head-ends, access control, elevators, metering. Record the vendor, firmware version, network path, and how the vendor connects for remote service.
  3. Find anything internet-exposed. Check your external attack surface for building system interfaces. Assume an exposed controller with old firmware will be found by someone else first.
  4. Segment and broker vendor access. Put building systems on their own network segments. Route vendor remote access through a monitored, MFA-protected path, not an always-on modem or shared password.
  5. Log and alert on setpoint changes. A temperature target changing at 2 a.m. is a security event until proven otherwise.
  6. Add a “suspected tampering” step to facilities runbooks. Before resetting a failed unit, capture configurations and logs. Preserving evidence costs minutes. Resetting first can erase the only clue.
  7. Patch or replace obsolete controllers. Danfoss’s own explanation of the French incident is about outdated devices. Put end-of-life controllers on the capital plan.

A hypothetical to test your plan: your pharmacy, lab, or cafeteria cold storage alarm goes off overnight. Does the on-call facilities tech know to call security? Does security know where the controller sits on the network? If either answer is “probably not,” you have found your gap.

The Bottom Line

The Pentagon investigation is reported, not concluded. Officials have not publicly confirmed an attack or named a culprit. You do not need a verdict to act on the lesson. If equipment on your network can change physical conditions, someone in your organization needs to own its security, and everyone needs to know who that is.

Exit mobile version