Blog · Threat intel · · 7 min read · by huntback Research

Typed by hand: how a Danfoss refrigeration controller is taken over

A French refrigeration installer photographed the change log of a Danfoss controller that was taken over on the evening of 23 October 2026. It shows two changes, made 22 minutes apart through the web interface: the password of user 1, then the store's name, rewritten to HACKED BY JUDRUD. We run Danfoss decoys built to look like those controllers. This is what that log means on the wire, who has come for our decoys, and what to check on your own controllers.

In brief

  • The published log shows a password change on Utilisateur 1, then, 22 minutes later, the Supervisor account renaming the store from "TEST" to "HACKED BY JUDRUD". Both went through the web interface ("via Web/XML").
  • Danfoss user guides describe the first user as the Supervisor level by factory default, so the first entry reads as the Supervisor's password being rewritten. It was the store name that was renamed, not an account.
  • Only two sources tried to log in to our Danfoss decoys, and both did it by hand, in a browser, with the factory default Supervisor / 12345.
  • One of them, 96.9.84[.]190, got in on its second try, spent seven minutes clicking through the inventory and configuration pages, changed nothing, then opened another controller.

The change log, line by line

On 25 October the French installer agyx_france posted a photo of a customer controller's trace log (Info > Tracage), captioned Sacré Judrud... Il a encore frappé ce week-end ! ("That Judrud... he struck again this weekend!")1. "Again" matters: the installer is describing a repeat visitor, not a first incident.

Danfoss controller trace log (Info, Tracage): entry 00859, 23/10/2026 21:55, Superviseur, Système via Web/XML, Nom Mag. TEST to HACKED BY JUDRUD; entry 00858, Utilisateurs via Web/XML, Utilisateur 1, Mot de passe changed
The controller's trace log, as the installer published it.
agyx_france Instagram post of 25 October 2026 with the trace log photo and the caption Sacré Judrud, il a encore frappé ce week-end
The installer's post, 25 October 2026.

Under a public post about the same incident, a technician at a second French refrigeration service company commented that a colleague had also had an attack from "this Judrud":

Public comment in French: Un collègue a eu une attaque de ce judurd (a colleague had an attack from this Judrud); the commenter's name and photo are blurred
"A colleague had an attack from this Judrud." We blurred the commenter's name and photo.

The two entries in the log:

EntryTime (device clock)AccountAreaChange
0085823/10/2026 21:33 (partly obscured)blurred in the photoUtilisateurs (via Web/XML)Utilisateur 1, Mot de passe: ******** -> ********
0085923/10/2026 21:55SuperviseurSystème (via Web/XML)Nom Mag.: TEST -> HACKED BY JUDRUD

Read in order (the log lists the newest entry first):

  1. "via Web/XML" means both changes came through the web interface, which talks XML to /xml.cgi. The browser front end and a script sending the same XML look identical here; what the entry rules out is the front panel or a local service tool.
  2. Utilisateur 1 is the first entry in the controller's user table. Danfoss guides describe the first user as the Supervisor level by factory default, with Supervisor / 12345 as the factory login56. Entry 00858 is a password change on that account, made by an account whose name the installer blurred.
  3. Twenty-two minutes later a Superviseur session changed Nom Mag., the store name. That is a calling card left for whoever opens the controller next, not, by itself, damage to the cold chain.

The installer's caption says the intruder first ran a bot to brute-force the customer account's password, then took over the Supervisor account.

the sequence behind the change log (23 Oct 2026, device clock)1. log inthe customeraccountper the installer2. 21:33Utilisateur 1password changedentry 008583. log inas Superviseur,new passwordfollows from the log4. 21:55store renamedHACKED BY JUDRUDentry 00859both recorded changes went through the web interface ("via Web/XML")
Steps 2 and 4 are the two log entries; step 1 is the installer's account; step 3 follows from the two entries.

The two changes on the wire

The controller's web interface reads and writes through one endpoint, POST /xml.cgi, with an XML command in the body. Reads such as read_units and read_list fill the pages; list writes (write_list) change tables such as the user list, and value writes (write_val) change single settings. The password change on user 1 and the store rename in the JUDRUD log are two such writes, recorded by the controller as "via Web/XML".

Who comes for our Danfoss decoys

Our Danfoss decoys are built as AK-SM 800A system managers with the StoreView interface and as the legacy AK-SM 800. They answer the factory login, Supervisor / 12345, and reply to every XML command the way an unpatched unit would. Almost everything that reaches them is the background noise every internet-facing address gets: crawlers, secret-file sweeps and generic probes. The few that were about these controllers came from people at a keyboard:

When (UTC)SourceWhat happened
3 Nov 19:44A Dutch home connection (address withheld)Chrome with a Dutch browser language opened a legacy controller's page, typed Supervisor / 12345 into the login form, and left.
5 Nov 06:47 to 06:5596.9.84[.]190, AS131207 (Cambodia)A privacy-focused Chromium browser (it sent the Sec-GPC header) loaded a legacy controller's login page and its scripts. 06:48:01: Supervisor / 123456, rejected. 06:48:25: Supervisor / 12345, accepted. Over the next seven minutes it clicked through the interface: four reads of the unit inventory and two reads of the configuration list. It wrote nothing.
5 Nov 07:0196.9.84[.]190Opened the StoreView page of another of our Danfoss decoys and did not log in. It touched nothing else in our fleet.
5 Nov 07:4737.140.223[.]186, AS206092 (Turkey)Loaded a legacy controller's home page with Referer: https://en.fofa.info/, the internet asset search engine. No login.

The successful session, as the decoy recorded it. The XML bodies are written by the page's own script, which follows the real web client; what the visitor chose was the password and the pages to open:

POST /xml.cgi                                     06:48:01  rejected
Content-Type: text/xml
<cmd user="Supervisor" password="123456" lang="English" version="C" action="getauth"></cmd>

POST /xml.cgi                                     06:48:25  accepted
<cmd user="Supervisor" password="12345" lang="English" version="C" action="getauth"></cmd>

POST /xml.cgi                                     06:48:25  home page
Aksm-Auth: Basic <Supervisor:12345, base64>
<cmd lang="English" version="C" action="read_units"></cmd>

POST /xml.cgi                                     06:55:31  configuration page
<cmd isconfigure="1" pnum="0" lang="English" version="C" action="read_list"></cmd>

Two hand-typed attempts with the same factory credentials, days apart, from unrelated networks. On these controllers, the first move we see is a person trying the password printed in the manual.

What to check on your controllers

  1. Read the trace log. In Info > Tracage (trace log), look for "(via Web/XML)" entries you did not make against Utilisateurs / Mot de passe or Nom Mag., and for a store name you did not set.
  2. Change every password, starting with user 1. Supervisor / 12345 is the factory login in Danfoss guides; it is the pair both of our hand-typed visitors tried. Remove accounts nobody uses.
  3. Watch the XML interface. If a proxy or firewall in front of the controller keeps request logs, look for POST /xml.cgi with action="write_list" or action="write_val", and getauth logins as Supervisor, from addresses that are not your maintenance provider's.
  4. Take the web interface off the internet. Reach it through a VPN or a protected management network agreed with your refrigeration provider.
  5. Update or replace. On the AK-SM 800A, version 4.2 fixes CVE-2025-41450 (the date-derived "code of the day" login) and 4.3.1 fixes CVE-2025-41451 and CVE-2025-41452234. Danfoss has said the older AK-SM 800 and AK-SC 355 no longer receive security updates9: isolate them.
  6. If you find a change you did not make, follow CERT-FR's guidance for these incidents: cut the internet exposure, reset to factory settings, reconfigure, and restore access through a secure connection7. The incidents have since spread beyond France8.

Indicators

IndicatorRoleConfidence
96.9.84[.]190Interactive login to a Danfoss decoy with Supervisor / 12345 (after 123456), read-only browsing, 5 Nov 2026High for the event
37.140.223[.]186FOFA-referred visit to a Danfoss decoy's home page, no login, 5 Nov 2026Context only
POST /xml.cgi with action="getauth" and user="Supervisor"Login to the controller's web interface; worth an alert from any unexpected addressPattern
POST /xml.cgi with action="write_list" or action="write_val"A change to users or settings through the web interfacePattern
HACKED BY JUDRUDStore name written into a compromised controller (published change log, 23 Oct 2026)High for that incident

References

  1. agyx_france, Instagram post with the controller's trace log, 25 October 2026.
  2. Danfoss, DSA-2025-03-01: improper authentication in the AK-SM8xxA Series (CVE-2025-41450, fixed in 4.2).
  3. Danfoss, DSA-2025-08-01: OS command injection and nginx configuration injection in the AK-SM8xxA Series (CVE-2025-41451 and CVE-2025-41452, fixed in 4.3.1).
  4. CISA, ICSA-25-140-03: Danfoss AK-SM 8xxA Series.
  5. Danfoss, AK-SM 800AL user guide (first user at Supervisor level by factory default; reset to Supervisor / 12345).
  6. Danfoss, AK-SM 850 manual (factory default user name Supervisor, password 12345).
  7. The Hacker News, coverage of the CERT-FR alert on refrigeration controllers, October 2026.
  8. Facilities Dive, European grocery stores hit with second refrigeration system hack, November 2026.
  9. Facilities Dive, Hack of Danfoss refrigeration controllers in Europe causes tens of millions in food losses, October 2026.