Skip to content
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

Viruses kdevtmpfsi and kinsing on packages/tracker/docker-compose.yml #73

Closed
plvo opened this issue Sep 13, 2024 · 17 comments
Closed

Viruses kdevtmpfsi and kinsing on packages/tracker/docker-compose.yml #73

plvo opened this issue Sep 13, 2024 · 17 comments

Comments

@plvo
Copy link

plvo commented Sep 13, 2024

I'm running on Ubuntu 22.04.

Since yesterday, my machine has been running the kdevtmpfsi and kinsing viruses. When I search for them, I find that they come from Docker (the Docker on this machine only runs the three project images).

The process of both viruses and especially kdevtmpfsi takes 100% of CPU performance (screen btop).
image
Yesterday I tried to stop it, and succeeded by uninstalling Docker directly, but after reconfiguring the repo, the processes reappeared.

I saw that you're using the postgres:16 image:


I found a very similar issue on the registery Docker Postgres repo: docker-library/postgres#1054

@damianharouff
Copy link

Yup. I posted it here already: #49

@GaloisField2718
Copy link

GaloisField2718 commented Sep 13, 2024

Have you changed every passwords in .env and tracker/docker/Bitcoin.conf?
And port too?

@damianharouff
Copy link

I have not. I don't run this garbage. I'm only a victim of the incompetence of whomever put together the instructions.

The documentation page:

1. Update `.env` file with your own configuration.
only states "Update with your own configuration". There's no statement to change every password in .env, and there's no statement at all to modify Bitcoin.conf.

Even if there were instructions, they won't be read by people just blindly copy and pasting the command blocks in a hurry to get to their FREE money.

@GaloisField2718
Copy link

Haha yes really not clear I updated on my branch.

@kagechio
Copy link

how to fully remove this sh1t?
Unfortunately, I'm running this on a server that is used to run other projects 💀

@GaloisField2718
Copy link

Normal.... first check for docker running with

docker ps -a

Look for Postgres:16, fractal-... and tracker.
Copy the id of each container and do

docker stop ID && docker remove ID

When you did this everything should be well removed.

@kagechio
Copy link

Normal.... first check for docker running with

docker ps -a

Look for Postgres:16, fractal-... and tracker. Copy the id of each container and do

docker stop ID && docker remove ID

When you did this everything should be well removed.

Thank You. CPU load is normal now. I'll let you know in a few hours if this doesn't come back

@plvo
Copy link
Author

plvo commented Sep 16, 2024

@kagechio if it reappears, and you can afford it, delete docker directly from your machine. It worked for me.

@damianharouff
Copy link

Yes good, throw everything away. :)

@kagechio
Copy link

@kagechio if it reappears, and you can afford it, delete docker directly from your machine. It worked for me.

That shit ain't coming back bro, thanks a lot @plvo @GaloisField2718 @damianharouff gbu

@kagechio
Copy link

{33668D8A-2DB7-407E-998F-8605FC5A261D}

@tushar1977
Copy link

first to do docker exec to enter to postgras , then go to /var/lib/postgresql/data/pgdata/pg_hba.conf and change host all all all scram-sha-256 to host all all all md5
then restart postgras container
do this to run tracker
sudo docker run -d
--name tracker
--add-host="host.docker.internal:host-gateway"
-e DATABASE_HOST="host.docker.internal"
-e RPC_HOST="host.docker.internal"
-e DATABASE_USERNAME="postgres"
-e DATABASE_PASSWORD="your_pass_that is entered in .env"
-e DATABASE_DB="postgres"
-p 3000:3000
tracker:latest

@damianharouff
Copy link

Other than making this situation worse, what's the point of reducing security by changing from one secure cipher to a very insecure cipher?

@tushar1977
Copy link

Other than making this situation worse, what's the point of reducing security by changing from one secure cipher to a very insecure cipher?

any solution ?

@damianharouff
Copy link

image

@tushar1977
Copy link

image

ok i tempory stopped by enabling ufw and only allowing specific ports and changed my postgres password

@opcatdev
Copy link
Collaborator

opcatdev commented Oct 8, 2024

#134

@opcatdev opcatdev closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants