HTTP DDOS

(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

2020-01-10T21:24:48.773205shield sshd\[15654\]: Invalid user P@ssw0rt123!@\# from 58.87.67.142 port 50250
2020-01-10T21:24:48.779210shield sshd\[15654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.67.142
2020-01-10T21:24:51.199180shield sshd\[15654\]: Failed password for invalid user P@ssw0rt123!@\# from 58.87.67.142 port 50250 ssh2
2020-01-10T21:27:24.431572shield sshd\[16420\]: Invalid user zhaohuan from 58.87.67.142 port 39068
2020-01-10T21:27:24.435273shield sshd\[16420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.67.142

Jan 10 23:48:08 localhost sshd\[22495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197  user=root
Jan 10 23:48:10 localhost sshd\[22495\]: Failed password for root from 132.232.7.197 port 50736 ssh2
Jan 10 23:50:40 localhost sshd\[22666\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197  user=root
Jan 10 23:50:42 localhost sshd\[22666\]: Failed password for root from 132.232.7.197 port 43984 ssh2
Jan 10 23:53:07 localhost sshd\[22692\]: Invalid user testing from 132.232.7.197
...

Jan 10 22:01:51 ns382633 sshd\[22546\]: Invalid user teste from 46.151.210.60 port 53292
Jan 10 22:01:51 ns382633 sshd\[22546\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.151.210.60
Jan 10 22:01:54 ns382633 sshd\[22546\]: Failed password for invalid user teste from 46.151.210.60 port 53292 ssh2
Jan 10 22:09:37 ns382633 sshd\[23708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.151.210.60  user=root
Jan 10 22:09:39 ns382633 sshd\[23708\]: Failed password for root from 46.151.210.60 port 45606 ssh2

Jan 10 23:37:02 mout sshd[31239]: Invalid user 123 from 101.231.124.6 port 58187

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

Unauthorized connection attempt detected from IP address 117.102.68.188 to port 22

Jan 10 22:10:06 grey postfix/smtpd\[27528\]: NOQUEUE: reject: RCPT from unknown\[62.4.55.56\]: 554 5.7.1 Service unavailable\; Client host \[62.4.55.56\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[62.4.55.56\]\; from=\ to=\ proto=ESMTP helo=\
...

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

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

1578692107 - 01/10/2020 22:35:07 Host: 45.172.144.206/45.172.144.206 Port: 445 TCP Blocked

Jan 10 18:48:29 : SSH login attempts with invalid user

Honeypot attack, port: 445, PTR: adsl.viettel.vn.

RDP Brute-Force (honeypot 7)

Honeypot attack, port: 445, PTR: 104.194.159.226.static.quadranet.com.