TerraMaster Forum

Hello.

Since i got my nas i enjoyed using it for the first few weeks, but noticed our drives were loud and overall system performance was meh.
After a bit of looking around i noticed i sadly felt victim of crypto-miners, they came through onto the host system and thus i reinstalled the whole machine.

Now less then 24h later, i checked dockhand, a nice tool to see your containers but i noticed this again:


It's the same exact issue as last time, but this time b/c i'm strictly running processes as a rootless user who can't do sudo, it didn't get so far to infect the crontab of the system and compromise it fully again.

I also only ran 2 containers, one of which is:

https://github.com/linuxserver/docker-q ... 4-r2-ls442

Which is up-to-date even with the version that came out yesterday.

So i delved in deeper, alot of users are using qbitorrent/that image and i don't hear anyone about any exploits, am i'm the only one?

I then checked docker and discovered this, and again i updated my ToS fully:



Seems ok? Well no because that docker engine version has ended it's support 9 MONTHS AGO!!
https://endoflife.date/docker-engine

And i wanted to update it like i'm used to with apt, but that's not the proper way to update the system/docker?

I have informed the relevant project team, and they are currently evaluating the update for Docker Engine.

The fact that the version did not change after you updated via apt may be related to the mirror source configuration. I will look into this further.

I suggest you try clearing any potentially affected containers and images, and then redeploy the system. If the issue is still related to the qBittorrent container, you can try changing the software source or temporarily use the qBittorrent version provided by the App Center. We will also relay this feedback to the lab and ask them to look into the matter.

RyanYang wrote: ↑22 Feb 2026, 23:00 I have informed the relevant project team, and they are currently evaluating the update for Docker Engine.

The fact that the version did not change after you updated via apt may be related to the mirror source configuration. I will look into this further.

I suggest you try clearing any potentially affected containers and images, and then redeploy the system. If the issue is still related to the qBittorrent container, you can try changing the software source or temporarily use the qBittorrent version provided by the App Center. We will also relay this feedback to the lab and ask them to look into the matter.

Thanks for your quick reply!

I didn't continue updating with apt, as the warning says it may break TOS, so i didn't continue updating it!
I'll redeploy it np i have it scripted, i use the none app center version as this one supports vuetorrent (custom ui frontend) and works a better for my usecase ! (I like to use ansible to deploy containers through ssh, makes it portable and easier to redeploy!)

RyanYang wrote: ↑22 Feb 2026, 23:00

Hi, any update so far ?

Hi. We have the intention to provide subsequent updates, but since there are many aspects involved, the feasibility and specific implementation methods are still under discussion.