“Widely used Daemon Tools disk app backdoored in monthlong
supply-chain attack” <https://arstechnica.com/security/2026/05/widely-used-daemon-tools-disk-app-backdoored-in-monthlong-supply-chain-attack/>:
Kaspersky, the security firm reporting the supply-chain attack,
said it began on April 8 and remained active as of the time its
post went live. Installers that are signed by the developer’s
official digital certificate and downloaded from its website
infect Daemon Tools executables, causing the malware to run at
boot time. Kaspersky didn’t explicitly say so, but based on
technical details, the infected versions appear to be only those
that run on Windows. Versions 12.5.0.2421 through 12.5.0.2434 are
affected. Neither Kaspersky nor developer AVB could be contacted
immediately for additional details.
Checking my Debian repo, I find a set of related packages named “daemontools”. But it seems clear to me this “daemontools” has nothing
to do with the “DAEMON Tools” product that is the subject of this security alert. To start with, the version numbers are quite
different.
Also, the latter is Windows-only <https://www.daemon-tools.cc/support/faq#system_requirements>, while
the former makes it quite clear <https://cr.yp.to/daemontools.html>
that it is “for managing UNIX services”.
“Widely used Daemon Tools disk app backdoored in monthlong
supply-chain attack” <https://arstechnica.com/security/2026/05/widely-used-daemon-tools-disk-app-backdoored-in-monthlong-supply-chain-attack/>:
Specifically, attackers tampered with legitimate application binaries
to execute malicious code at process startup and leveraged a legitimate >Windows service to maintain persistence on the host.
Why the Windows one uses the term "daemon" when it has nothing to do
with daemons I don't know.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,116 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 85:27:28 |
| Calls: | 14,305 |
| Files: | 186,338 |
| D/L today: |
647 files (184M bytes) |
| Messages: | 2,525,478 |