Jan 10 22:10:57 grey postfix/smtpd\[30698\]: NOQUEUE: reject: RCPT from unknown\[188.163.99.212\]: 554 5.7.1 Service unavailable\; Client host \[188.163.99.212\] blocked using cbl.abuseat.org\; Blocked - see http://www.abuseat.org/lookup.cgi\?ip=188.163.99.212\; from=\ to=\ proto=ESMTP helo=\<188-163-99-212.broadband.kyivstar.net\>
...

Jan 10 22:10:25 serwer sshd\[25861\]: User sshd from 118.25.3.29 not allowed because not listed in AllowUsers
Jan 10 22:10:25 serwer sshd\[25861\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.3.29  user=sshd
Jan 10 22:10:27 serwer sshd\[25861\]: Failed password for invalid user sshd from 118.25.3.29 port 44881 ssh2
...

\[Fri Jan 10 22:10:29 2020\] \[error\] \[client 185.100.87.247\] client denied by server configuration: /var/www/html/default/nmaplowercheck1578690629
\[Fri Jan 10 22:10:30 2020\] \[error\] \[client 185.100.87.247\] client denied by server configuration: /var/www/html/default/HNAP1
\[Fri Jan 10 22:10:30 2020\] \[error\] \[client 185.100.87.247\] client denied by server configuration: /var/www/html/default/
...

Jan 10 23:06:47 herz-der-gamer sshd[11306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.17  user=root
Jan 10 23:06:50 herz-der-gamer sshd[11306]: Failed password for root from 222.186.180.17 port 27180 ssh2
Jan 10 23:06:53 herz-der-gamer sshd[11306]: Failed password for root from 222.186.180.17 port 27180 ssh2
Jan 10 23:06:47 herz-der-gamer sshd[11306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.17  user=root
Jan 10 23:06:50 herz-der-gamer sshd[11306]: Failed password for root from 222.186.180.17 port 27180 ssh2
Jan 10 23:06:53 herz-der-gamer sshd[11306]: Failed password for root from 222.186.180.17 port 27180 ssh2
...

(From eric@talkwithcustomer.com) Hello wardchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website wardchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website wardchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one f

Invalid user lg from 146.168.2.84 port 41322

20/1/10@17:15:15: FAIL: IoT-SSH address from=95.213.184.222
...

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

Jan 10 22:36:22 debian-2gb-nbg1-2 kernel: \[951491.484536\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.18 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=41862 PROTO=TCP SPT=45372 DPT=24001 WINDOW=1024 RES=0x00 SYN URGP=0

SSH Brute Force, server-1 sshd[12939]: Failed password for root from 183.82.0.15 port 63674 ssh2

Caught in portsentry honeypot

Jan 10 22:11:02 grey postfix/smtpd\[27528\]: NOQUEUE: reject: RCPT from adsl196-5-201-206-196.adsl196-7.iam.net.ma\[196.206.201.5\]: 554 5.7.1 Service unavailable\; Client host \[196.206.201.5\] blocked using dul.dnsbl.sorbs.net\; Dynamic IP Addresses See: http://www.sorbs.net/lookup.shtml\?196.206.201.5\; from=\ to=\ proto=ESMTP helo=\
...

MultiHost/MultiPort Probe, Scan, Hack -

Honeypot attack, port: 445, PTR: PTR record not found

firewall-block, port(s): 23/tcp