4 ms·
I never have exposed this container to the world ever, and my server do report the existence of such binary. That is the reason based on CPU usage I suspect tha
by wok4899 1y ago
I never have exposed this container to the world ever, and my server do report the existence of such binary. That is the reason based on CPU usage I suspect that mining never triggered.
> ps -ef | grep netservlet
> root 3708105 3665360 0 08:06 pts/2 00:00:00 grep netservlet
- bakugo 1y agoHow long have you been running this container? Can you check the contents of your qBittorrent.conf?
- thephyber 1y agoEdit: absolutely make sure you are running the newest version of the image. It patches security issues in the app. Read this article: https://torrentfreak.com/qbittorrent-web-ui-exploited-to-mine-cryptocurrency-heres-how-to-fix-230902/ https://torrentfreak.com/qbittorrent-web-ui-exploited-to-min... It mentions the app will use uPnP to expose itself automatically. Remember that BitTorrent protocol is P2P, so it likely is accessible from the internet. My suggestion is to wipe the image, update pull/run the newest version, and change the admin credentials after it starts up.
- iogjoertsnbu 1y agothat's just grep showing you your own grep process lol. you can do ps -ef | grep foobarbaroof and get the same thing...