AI
Coldframe Simulates Supermarket Refrigeration Controllers to Record Attack Behavior
Hacker News project Coldframe is a honeypot for supermarket refrigeration controllers that can impersonate a Danfoss AK-SM 800A or Dixell XWEB EVO and record connection sources, attempted passwords, and public vulnerability exploits. The project is a single Python file with no third-party dependencies.
The project background says that in 2026, attackers in Europe used default passwords and old, unpatched firmware to break into internet-connected refrigeration monitoring equipment and forcibly trigger defrost cycles. Coldframe attracts attackers by simulating these controllers, but it is not connected to any real equipment. It can record who initiates connections, which passwords are attempted, which public vulnerability exploits are used, and what control actions attackers take after logging in.
The Danfoss impersonation replicates characteristics observed by internet scanners on a real AK-SM 800A, including nginx server headers and header order, the Danfoss StoreView page title, support only for TLS 1.2, and a one-year self-signed certificate with CN=DanfossSM800A; each build generates an independent key. Weak passwords and the correct CVE-2025-41450 “daily code” can log in, after which attackers receive a session token and a dashboard with fake refrigeration cases and defrost buttons.
The Dixell impersonation simulates the response headers, resource paths, and page sizes of a real XWEB EVO and uses the real /cgi-bin/login.lua login flow; the factory default Admin/Admin can log in successfully, five failures within five minutes trigger a lockout, and attempts at CVE-2026-25085 authentication bypass are flagged. The project can also identify multiple types of public Danfoss and XWEB vulnerabilities and can optionally enable a Modbus TCP service providing fake case temperatures, setpoints, and defrost registers to catch general industrial scanners. Because the icons and some pages belong to vendor materials, the repository does not directly include those files; deployers can configure them through local files when they have the right to use them.