The malicious code arrived in Testing and Unstable. If it recognized that it had landed on a system that does not work with systemd, it did nothing. But it was still there. This is an obvious security problem. Malicious code lurking in the system. Nobody can say if, how and when it can become active and cause damage. Thank God it has been found. But that should be a lesson to us. Security will have to become more important in the future.

Here is a timeline of what happened:
https://research.swtch.com/xz-timeline

So far, I have found everything I need at Devuan.

Thank you, quickfur. That must be the case. I've never thought about it before, but I like it.

Yes, o.k., altoid. When I think about all this, I'm currently coming to the conclusion that I'm actually stupid if I don't continue working with X11. I assumed that Wayland was less bloated than Wayland. At least that's what I've read several times in various forums. I've also read that Wayland is more cleanly programmed and much clearer. I personally cannot verify these statements. What I do know is that I have more problems with Wayland. For example, when I have to fill in long tables from various authorities online, I only have problems with Wayland because the clipboard doesn't work reliably. And here it's pretty stupid if the penultimate number is pasted instead of the last number you copied. If you have to enter several hindered amounts, you simply can't work with Wayland. OK, I'll continue working with X11 for the time being. Many thanks for the input. I'm still interested in the topic and maybe I can read more interesting thoughts in this forum.
Best regards

Yes, that's probably a gap, semil. Although I still have problems with the clipboard, for example, I've only been using Wayland for some time now. It's a stupid situation. Not everything actually works perfectly with Wayland, but with X11 there are apparently security holes that aren't being fixed.

Thank you

Yes, thank you very much FOSSenjoyer! I much prefer it that way, of course.

Yes.

uname -a
 ... 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux

Addendum: did this bug break anything for anyone? I can't see that anything is broken here.
Addendum 2: Is this perhaps different with Devuan because no systemd is used?

but it is interesting that it also works on Devuan ;-)
Update, 2023-11-05 09:38:
Yes, I just realized it. Constant updates keep everything up to date, but it's a terrible use of resources on the net. It was an interesting experience for me, but I won't be using Nightly any more.

That was an interesting execution! I am now venturing into Ceres on my second system. Thanks for the tips.