• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

How to deal with unknown outbound ftp-traffic

Noturns

Regular Pleskian
According to my server logs i have some unattended outbound or inbound ftp traffic on my server which should not be there.

Code:
May 20 17:20:34 vps2 proftpd[24091]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:21:31 vps2 xinetd[1480]: START: ftp pid=27685 from=::ffff:xx.xx.xx.xx
May 20 17:21:33 vps2 proftpd[27685]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:22:31 vps2 xinetd[1480]: START: ftp pid=28209 from=::ffff:xx.xx.xx.xx
May 20 17:22:33 vps2 proftpd[28209]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:23:31 vps2 xinetd[1480]: START: ftp pid=28719 from=::ffff:xx.xx.xx.xx
May 20 17:23:33 vps2 proftpd[28719]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:24:31 vps2 xinetd[1480]: START: ftp pid=29236 from=::ffff:xx.xx.xx.xx
May 20 17:24:34 vps2 proftpd[29236]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:25:31 vps2 xinetd[1480]: START: ftp pid=29737 from=::ffff:xx.xx.xx.xx
May 20 17:25:33 vps2 proftpd[29737]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:26:32 vps2 xinetd[1480]: START: ftp pid=30253 from=::ffff:xx.xx.xx.xx
May 20 17:26:34 vps2 proftpd[30253]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:27:31 vps2 xinetd[1480]: START: ftp pid=30763 from=::ffff:xx.xx.xx.xx
May 20 17:27:31 vps2 proftpd[30763]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session opened.
May 20 17:27:33 vps2 proftpd[30763]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.
May 20 17:28:31 vps2 xinetd[1480]: START: ftp pid=31271 from=::ffff:xx.xx.xx.xx
May 20 17:28:33 vps2 proftpd[31271]: 127.0.0.1 (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.

I noticed multiple PIDs in the logs. It looks like the script is blocked because the FTP session is closed after a few seconds. I'm pretty sure that we have a white-list all two trusted IP adresses. We also checked the Fail2Ban and that ip address xx.xx.xx.xx is not listed there.

Update:
I have removed a subscription of a previous customer of ours. The server-logs now state the following command:
Code:
May 20 17:51:32 vps2 sshd[7725]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key
May 20 17:51:32 vps2 sshd[7725]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key

As a temporarily precaution i have added a rule in my firewall to block that ip-address.

I would like to know what script is causing this and how to approach this situation?
How can i trace proftpd or xinetd or find a string in a batchscript?

Here is my server specs
Version Plesk v12.5.30_build1205150826.19
OS CentOS 6.7 (Final)
 
Back
Top