Someone trying to break in...

[crobinson]

So I have fail2ban working I noticed something odd. I have SSH locked down to just a few IPs but I noticed someone trying to hack in via SSH. Here is a snip from my secure log.

Mar 18 00:18:14 ns1 sshd[15416]: Failed password for root from 116.10.191.164 port 3003 ssh2
Mar 18 00:18:14 ns1 unix_chkpwd[15426]: password check failed for user (root)
Mar 18 00:18:14 ns1 sshd[15416]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:15 ns1 sshd[15418]: Failed password for root from 116.10.191.164 port 1362 ssh2
Mar 18 00:18:15 ns1 unix_chkpwd[15427]: password check failed for user (root)
Mar 18 00:18:15 ns1 sshd[15418]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:16 ns1 sshd[15416]: Failed password for root from 116.10.191.164 port 3003 ssh2
Mar 18 00:18:16 ns1 unix_chkpwd[15428]: password check failed for user (root)
Mar 18 00:18:16 ns1 sshd[15416]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:17 ns1 sshd[15418]: Failed password for root from 116.10.191.164 port 1362 ssh2
Mar 18 00:18:18 ns1 unix_chkpwd[15429]: password check failed for user (root)
Mar 18 00:18:18 ns1 sshd[15418]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:18 ns1 sshd[15416]: Failed password for root from 116.10.191.164 port 3003 ssh2
Mar 18 00:18:18 ns1 unix_chkpwd[15430]: password check failed for user (root)
Mar 18 00:18:18 ns1 sshd[15416]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:19 ns1 sshd[15418]: Failed password for root from 116.10.191.164 port 1362 ssh2
Mar 18 00:18:20 ns1 sshd[15416]: Failed password for root from 116.10.191.164 port 3003 ssh2

Odd that I am seeing different ports and I am unsure how they are trying to hack in. Does anyone have any ideas?

BTW fail2ban is a must... I hope it makes it into Plesk 12.

 

[IgorG]

BTW fail2ban is a must... I hope it makes it into Plesk 12.

http://download1.parallels.com/Plesk/PP12/parallels-plesk-12.0-for-linux-change-log.html

Fail2ban support. Now administrators can protect their servers from different kinds of attacks. Fail2ban, a popular intrusion prevention system, protects SSH, FTP, web, and mail services. It detects suspicious activity and temporarily blocks the IP addresses of hosts that are trying to breach the system's security. The default ban time is 10 minutes. Administrators can configure Fail2ban in Tools & Settings > IP Address Banning (Fail2Ban).

 

[crobinson]

Mar 18 00:18:18 ns1 unix_chkpwd[15429]: password check failed for user (root)
Mar 18 00:18:18 ns1 sshd[15418]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:18 ns1 sshd[15416]: Failed password for root from 116.10.191.164 port 3003 ssh2
Mar 18 00:18:18 ns1 unix_chkpwd[15430]: password check failed for user (root)
Mar 18 00:18:18 ns1 sshd[15416]: Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
Mar 18 00:18:19 ns1 sshd[15418]: Failed password for root from 116.10.191.164 port 1362 ssh2

Does anyone have any ideas on how they are able to trip SSH alarm using a non-opened port?

 

[Shanats]

Hi crobinson, you should look into ssh key and disable ssh login.

 

[crobinson]

I did think about that.... There are only a few people that need that kind of access. I am just wondering how they are initiating the SSH login even tho the SSH port 22 is locked down to allow a few IPs and deny 99.99% of the internet.

 

[KristianM]

Hi,

in that case you should check your iptables rules

Regards,
Kristian

 

[Shanats]

You should also consider changing your ssh port from default 22 to something above 1024.

I did think about that.... There are only a few people that need that kind of access. I am just wondering how they are initiating the SSH login even tho the SSH port 22 is locked down to allow a few IPs and deny 99.99% of the internet.