7,32-07/07 [bc04/m105] PostRequest-Spammer scoring: essen

(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with svchiropractic.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any

suspicious action Tue, 03 Mar 2020 10:20:15 -0300

suspicious action Tue, 03 Mar 2020 10:20:33 -0300

(From eric@talkwithcustomer.com) Hello naturalhealthdcs.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 naturalhealthdcs.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 naturalhealthdcs.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

Nov 11 23:34:53 zimbra sshd[18494]: Invalid user javiar from 107.175.92.26
Nov 11 23:34:53 zimbra sshd[18494]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.26
Nov 11 23:34:55 zimbra sshd[18494]: Failed password for invalid user javiar from 107.175.92.26 port 33334 ssh2
Nov 11 23:34:55 zimbra sshd[18494]: Received disconnect from 107.175.92.26 port 33334:11: Bye Bye [preauth]
Nov 11 23:34:55 zimbra sshd[18494]: Disconnected from 107.175.92.26 port 33334 [preauth]
Nov 12 02:07:47 zimbra sshd[2528]: Invalid user hakkaku from 107.175.92.26
Nov 12 02:07:47 zimbra sshd[2528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.26
Nov 12 02:07:49 zimbra sshd[2528]: Failed password for invalid user hakkaku from 107.175.92.26 port 35062 ssh2
Nov 12 02:07:49 zimbra sshd[2528]: Received disconnect from 107.175.92.26 port 35062:11: Bye Bye [preauth]
Nov 12 02:07:49 zimbra sshd[2528]........
-------------------------------

Nov 14 07:40:18 sd-53420 sshd\[10527\]: Invalid user heyerdal from 107.175.92.26
Nov 14 07:40:18 sd-53420 sshd\[10527\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.26
Nov 14 07:40:20 sd-53420 sshd\[10527\]: Failed password for invalid user heyerdal from 107.175.92.26 port 54692 ssh2
Nov 14 07:44:07 sd-53420 sshd\[11561\]: Invalid user appenzeller from 107.175.92.26
Nov 14 07:44:07 sd-53420 sshd\[11561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.26
...

Aug 30 02:24:44 site2 sshd\[52555\]: Invalid user kipl from 107.175.92.173Aug 30 02:24:46 site2 sshd\[52555\]: Failed password for invalid user kipl from 107.175.92.173 port 48828 ssh2Aug 30 02:29:02 site2 sshd\[52640\]: Failed password for ftp from 107.175.92.173 port 46812 ssh2Aug 30 02:33:15 site2 sshd\[52729\]: Invalid user matt from 107.175.92.173Aug 30 02:33:18 site2 sshd\[52729\]: Failed password for invalid user matt from 107.175.92.173 port 47020 ssh2
...

SSH invalid-user multiple login attempts

Aug 19 00:58:28 php1 sshd\[1614\]: Invalid user display from 107.175.92.132
Aug 19 00:58:28 php1 sshd\[1614\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.132
Aug 19 00:58:30 php1 sshd\[1614\]: Failed password for invalid user display from 107.175.92.132 port 40520 ssh2
Aug 19 01:02:50 php1 sshd\[1986\]: Invalid user admin from 107.175.92.132
Aug 19 01:02:50 php1 sshd\[1986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.132

Aug 16 07:48:36 sachi sshd\[26569\]: Invalid user 123456 from 107.175.92.134
Aug 16 07:48:36 sachi sshd\[26569\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.134
Aug 16 07:48:38 sachi sshd\[26569\]: Failed password for invalid user 123456 from 107.175.92.134 port 38910 ssh2
Aug 16 07:53:12 sachi sshd\[26927\]: Invalid user cw from 107.175.92.134
Aug 16 07:53:12 sachi sshd\[26927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.134

Aug 16 00:43:34 localhost sshd\[6668\]: Invalid user applmgr from 107.175.92.132
Aug 16 00:43:34 localhost sshd\[6668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.132
Aug 16 00:43:36 localhost sshd\[6668\]: Failed password for invalid user applmgr from 107.175.92.132 port 59010 ssh2
Aug 16 00:47:53 localhost sshd\[6823\]: Invalid user alvin from 107.175.92.132
Aug 16 00:47:53 localhost sshd\[6823\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.132
...

Aug  9 03:58:34 db sshd\[21255\]: Invalid user knight from 107.175.92.134
Aug  9 03:58:34 db sshd\[21255\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.134 
Aug  9 03:58:36 db sshd\[21255\]: Failed password for invalid user knight from 107.175.92.134 port 39104 ssh2
Aug  9 04:03:31 db sshd\[21322\]: Invalid user eti from 107.175.92.134
Aug  9 04:03:31 db sshd\[21322\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.92.134 
...

Dec 15 00:45:39 legacy sshd[32434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.246.161.60
Dec 15 00:45:40 legacy sshd[32434]: Failed password for invalid user hiawatha from 52.246.161.60 port 41574 ssh2
Dec 15 00:52:42 legacy sshd[366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.246.161.60
...

ET DROP Dshield Block Listed Source group 1 - port: 56880 proto: TCP cat: Misc Attack

Dec 14 08:18:48 server sshd\[31290\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.213.214.225 
Dec 14 08:18:50 server sshd\[31290\]: Failed password for invalid user hung from 81.213.214.225 port 55314 ssh2
Dec 15 01:54:05 server sshd\[19258\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.213.214.225  user=root
Dec 15 01:54:06 server sshd\[19258\]: Failed password for root from 81.213.214.225 port 37247 ssh2
Dec 15 02:30:46 server sshd\[30583\]: Invalid user alfano from 81.213.214.225
Dec 15 02:30:46 server sshd\[30583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.213.214.225 
...

2019-12-14T17:46:11.669571ns547587 sshd\[2822\]: Invalid user seren from 198.1.65.159 port 35466
2019-12-14T17:46:11.672799ns547587 sshd\[2822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.sasianet.com
2019-12-14T17:46:13.300115ns547587 sshd\[2822\]: Failed password for invalid user seren from 198.1.65.159 port 35466 ssh2
2019-12-14T17:51:15.600512ns547587 sshd\[11077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.sasianet.com  user=root
...

SSH bruteforce

--- report ---
Dec 14 20:22:39 sshd: Connection from 218.92.0.172 port 25596
Dec 14 20:22:40 sshd: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.172  user=root
Dec 14 20:22:41 sshd: Failed password for root from 218.92.0.172 port 25596 ssh2
Dec 14 20:22:42 sshd: Disconnected from authenticating user root 218.92.0.172 port 25596 [preauth]
Dec 14 20:22:42 sshd: Received disconnect from 218.92.0.172 port 25596:11:  [preauth]

Dec 15 05:02:25 vibhu-HP-Z238-Microtower-Workstation sshd\[11275\]: Invalid user jn from 118.24.74.84
Dec 15 05:02:25 vibhu-HP-Z238-Microtower-Workstation sshd\[11275\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.74.84
Dec 15 05:02:27 vibhu-HP-Z238-Microtower-Workstation sshd\[11275\]: Failed password for invalid user jn from 118.24.74.84 port 43284 ssh2
Dec 15 05:08:12 vibhu-HP-Z238-Microtower-Workstation sshd\[11698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.74.84  user=gdm
Dec 15 05:08:14 vibhu-HP-Z238-Microtower-Workstation sshd\[11698\]: Failed password for gdm from 118.24.74.84 port 35698 ssh2
...

185.2.4.37 - - \[14/Dec/2019:23:53:12 +0100\] "POST /wp-login.php HTTP/1.0" 200 7556 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
185.2.4.37 - - \[14/Dec/2019:23:53:13 +0100\] "POST /wp-login.php HTTP/1.0" 200 7381 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
185.2.4.37 - - \[14/Dec/2019:23:53:14 +0100\] "POST /wp-login.php HTTP/1.0" 200 7376 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"

Dec 15 00:32:00 localhost sshd\[18766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.220.190  user=root
Dec 15 00:32:02 localhost sshd\[18766\]: Failed password for root from 115.159.220.190 port 60676 ssh2
Dec 15 00:39:03 localhost sshd\[27222\]: Invalid user Liebert from 115.159.220.190 port 34428

Dec 15 01:30:21 sauna sshd[104750]: Failed password for root from 103.253.3.158 port 52480 ssh2
...

Brute force attempt

2019-12-14T18:44:02.264067xentho-1 sshd[55631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.202  user=root
2019-12-14T18:44:04.735635xentho-1 sshd[55631]: Failed password for root from 222.186.175.202 port 34784 ssh2
2019-12-14T18:44:08.682689xentho-1 sshd[55631]: Failed password for root from 222.186.175.202 port 34784 ssh2
2019-12-14T18:44:02.264067xentho-1 sshd[55631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.202  user=root
2019-12-14T18:44:04.735635xentho-1 sshd[55631]: Failed password for root from 222.186.175.202 port 34784 ssh2
2019-12-14T18:44:08.682689xentho-1 sshd[55631]: Failed password for root from 222.186.175.202 port 34784 ssh2
2019-12-14T18:44:02.264067xentho-1 sshd[55631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.202  user=root
2019-12-14T18:44:04.735635xentho-1 sshd[55631]: Failed password for roo
...

Dec 15 01:19:12 markkoudstaal sshd[31888]: Failed password for root from 222.186.180.9 port 36224 ssh2
Dec 15 01:19:15 markkoudstaal sshd[31888]: Failed password for root from 222.186.180.9 port 36224 ssh2
Dec 15 01:19:24 markkoudstaal sshd[31888]: Failed password for root from 222.186.180.9 port 36224 ssh2
Dec 15 01:19:24 markkoudstaal sshd[31888]: error: maximum authentication attempts exceeded for root from 222.186.180.9 port 36224 ssh2 [preauth]

sshd jail - ssh hack attempt

Dec 15 00:49:58 vpn01 sshd[2062]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.81.4.235
Dec 15 00:50:00 vpn01 sshd[2062]: Failed password for invalid user alper123 from 206.81.4.235 port 47960 ssh2
...