-
Notifications
You must be signed in to change notification settings - Fork 2k
kdevtmpfsi virus use 99% of cpu #1127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
How do you start the container? Is your setup similar to the one described in #1110 |
docker compose file
my php Dockerfile
|
Same cause as in #1110 . With this, you open your php fpm instance to the WWW. |
tank you |
There was also a lot of discussion on this malware over at redis/docker-library-redis#217 (comment) If you want more information you could look through the other issues we've had https://github.com/issues?q=is:issue+org:docker-library+kdevtmpfsi Going to close since this seems resolved |
Is it enough? I'm unsure. You can close the listening port (incoming). But it may have some outgoing connection (also known as reverse connection). ps. the @wglambert links seem good references |
(Locking this for the same reason as in redis/docker-library-redis#217 (comment) -- if you've been hacked, you need to perform appropriate remediation on your server and deployments, and the details of that remediation is out of scope for this repository.) |
hello
i use php:7.3-fpm in my project
5 minute after start container kdevtmpfsi proccess started and use all cpu
file exist in :
/tmp/kdevtmpfsi
The text was updated successfully, but these errors were encountered: