Dec 25 09:14:56 MK-Soft-VM7 sshd[3288]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.241.244.93 
Dec 25 09:14:58 MK-Soft-VM7 sshd[3288]: Failed password for invalid user test from 121.241.244.93 port 35715 ssh2
...

2019-12-25T09:09:54.000739tmaserv sshd\[15242\]: Failed password for root from 125.140.242.236 port 43156 ssh2
2019-12-25T10:24:31.793916tmaserv sshd\[18383\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.140.242.236  user=root
2019-12-25T10:24:33.610866tmaserv sshd\[18383\]: Failed password for root from 125.140.242.236 port 47578 ssh2
2019-12-25T10:39:28.330818tmaserv sshd\[21444\]: Invalid user maid from 125.140.242.236 port 48452
2019-12-25T10:39:28.337539tmaserv sshd\[21444\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.140.242.236
2019-12-25T10:39:30.629744tmaserv sshd\[21444\]: Failed password for invalid user maid from 125.140.242.236 port 48452 ssh2
...

12/25/2019-10:19:33.225763 185.175.93.34 Protocol: 6 ET DROP Dshield Block Listed Source group 1

Unauthorized connection attempt from IP address 171.233.164.118 on Port 445(SMB)

Unauthorized connection attempt detected from IP address 61.8.71.28 to port 445

Dec 25 07:11:45 mxgate1 postfix/postscreen[20302]: CONNECT from [51.254.178.113]:43595 to [176.31.12.44]:25
Dec 25 07:11:45 mxgate1 postfix/dnsblog[20304]: addr 51.254.178.113 listed by domain zen.spamhaus.org as 127.0.0.3
Dec 25 07:11:51 mxgate1 postfix/postscreen[20302]: DNSBL rank 2 for [51.254.178.113]:43595
Dec 25 07:11:51 mxgate1 postfix/tlsproxy[20368]: CONNECT from [51.254.178.113]:43595
Dec x@x
Dec 25 07:11:51 mxgate1 postfix/postscreen[20302]: DISCONNECT [51.254.178.113]:43595
Dec 25 07:11:51 mxgate1 postfix/tlsproxy[20368]: DISCONNECT [51.254.178.113]:43595


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=51.254.178.113

2019-12-25 00:26:08 H=(ylmf-pc) [116.239.254.100]:50653 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
2019-12-25 00:26:14 H=(ylmf-pc) [116.239.254.100]:50186 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
2019-12-25 00:26:20 H=(ylmf-pc) [116.239.254.100]:50703 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
...

Dec 25 07:26:29 DAAP sshd[18198]: Invalid user jeff from 119.123.216.72 port 2053
Dec 25 07:26:29 DAAP sshd[18198]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.216.72
Dec 25 07:26:29 DAAP sshd[18198]: Invalid user jeff from 119.123.216.72 port 2053
Dec 25 07:26:31 DAAP sshd[18198]: Failed password for invalid user jeff from 119.123.216.72 port 2053 ssh2
Dec 25 07:30:17 DAAP sshd[18245]: Invalid user piram from 119.123.216.72 port 2054
...

port scan and connect, tcp 80 (http)

2019-12-25T06:26:17.837281abusebot-7.cloudsearch.cf sshd[27934]: Invalid user benoit from 164.132.197.108 port 39304
2019-12-25T06:26:17.842499abusebot-7.cloudsearch.cf sshd[27934]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.ip-164-132-197.eu
2019-12-25T06:26:17.837281abusebot-7.cloudsearch.cf sshd[27934]: Invalid user benoit from 164.132.197.108 port 39304
2019-12-25T06:26:20.281214abusebot-7.cloudsearch.cf sshd[27934]: Failed password for invalid user benoit from 164.132.197.108 port 39304 ssh2
2019-12-25T06:28:29.001368abusebot-7.cloudsearch.cf sshd[27936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.ip-164-132-197.eu  user=root
2019-12-25T06:28:30.254948abusebot-7.cloudsearch.cf sshd[27936]: Failed password for root from 164.132.197.108 port 32872 ssh2
2019-12-25T06:30:34.156775abusebot-7.cloudsearch.cf sshd[27940]: Invalid user backup from 164.132.197.108 port 54672
...

Unauthorized connection attempt detected from IP address 114.34.208.127 to port 1433

(From edwardfrankish32@gmail.com) Hi!

Did you know that the first page of Goggle search results is where all potential clients will be looking at if they're searching for products/services? Does your website appear on the first page of Google search results when you try searching for your products/services? Most of the time, they would just ignore page 2 and so on since the results listed on the first page seem more relevant and are more credible.

I'm very familiar with all the algorithms and methods that search engines use and I am an expert on how to get the most out of it. I'm a freelance online marketing specialist, and I have helped my clients bring their websites to the first page of web searches for more than 10 years now. Also, the cost of my services is something that small businesses can afford.

I can give you a free consultation so you can be better informed of how your website is doing right now, what can be done and what to expect after if this is something that interests you. Kindly wri

/var/log/messages:Dec 25 06:08:18 sanyalnet-cloud-vps audispd: node=sanyalnet-cloud-vps.freeddns.org type=CRYPTO_SESSION msg=audhostname(1577254098.699:76686): pid=9146 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-server cipher=aexxxxxxx28-ctr ksize=128 mac=hmac-sha2-256 pfs=ecdh-sha2-nistp256 spid=9147 suid=74 rport=60580 laddr=104.167.106.93 lport=22  exe="/usr/sbin/sshd" hostname=? addr=1.2.144.85 terminal=? res=success'
/var/log/messages:Dec 25 06:08:18 sanyalnet-cloud-vps audispd: node=sanyalnet-cloud-vps.freeddns.org type=CRYPTO_SESSION msg=audhostname(1577254098.703:76687): pid=9146 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-client cipher=aexxxxxxx28-ctr ksize=128 mac=hmac-sha2-256 pfs=ecdh-sha2-nistp256 spid=9147 suid=74 rport=60580 laddr=104.167.106.93 lport=22  exe="/usr/sbin/sshd" hostname=? addr=1.2.144.85 terminal=? res=success'
/var/log/messages:Dec 25 06:08:20 sanyalnet-cloud-vps fail2ban.filter[1551]: INFO [ssh........
-------------------------------

Host Scan

$f2bV_matches