2020-06-14 14:03:58.310788-0500  localhost sshd[67357]: Failed password for invalid user mohamed from 176.31.255.63 port 52006 ssh2

2020-06-14T18:32:41+0200 Failed SSH Authentication/Brute Force Attack. (Server 4)

2020-06-14T18:22:20.389084abusebot.cloudsearch.cf sshd[27854]: Invalid user wallace from 139.198.5.79 port 33748
2020-06-14T18:22:20.394765abusebot.cloudsearch.cf sshd[27854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79
2020-06-14T18:22:20.389084abusebot.cloudsearch.cf sshd[27854]: Invalid user wallace from 139.198.5.79 port 33748
2020-06-14T18:22:23.081606abusebot.cloudsearch.cf sshd[27854]: Failed password for invalid user wallace from 139.198.5.79 port 33748 ssh2
2020-06-14T18:25:28.726874abusebot.cloudsearch.cf sshd[28085]: Invalid user cym from 139.198.5.79 port 55542
2020-06-14T18:25:28.732257abusebot.cloudsearch.cf sshd[28085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79
2020-06-14T18:25:28.726874abusebot.cloudsearch.cf sshd[28085]: Invalid user cym from 139.198.5.79 port 55542
2020-06-14T18:25:30.560987abusebot.cloudsearch.cf sshd[28085]: Failed password for invalid
...

Jun 14 20:29:13 mellenthin sshd[10636]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.211  user=root
Jun 14 20:29:15 mellenthin sshd[10636]: Failed password for invalid user root from 185.220.101.211 port 2708 ssh2

(sshd) Failed SSH login from 163.172.62.124 (FR/France/163-172-62-124.rev.poneytelecom.eu): 5 in the last 3600 secs

(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drtomalin.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software that can

 TCP (SYN) 195.54.160.155:49700 -> port 32433, len 44

$f2bV_matches

Brute force attempt

Automatic report - Port Scan Attack

Jun 14 15:07:46 abendstille sshd\[10697\]: Invalid user charlesm from 109.234.39.92
Jun 14 15:07:46 abendstille sshd\[10697\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.234.39.92
Jun 14 15:07:48 abendstille sshd\[10697\]: Failed password for invalid user charlesm from 109.234.39.92 port 55932 ssh2
Jun 14 15:11:27 abendstille sshd\[14550\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.234.39.92  user=root
Jun 14 15:11:29 abendstille sshd\[14550\]: Failed password for root from 109.234.39.92 port 60422 ssh2
...

Jun 14 15:49:16 piServer sshd[20184]: Failed password for root from 119.29.173.247 port 56536 ssh2
Jun 14 15:52:55 piServer sshd[20484]: Failed password for root from 119.29.173.247 port 36152 ssh2
Jun 14 15:56:44 piServer sshd[20770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.173.247 
...

Unauthorized access detected from black listed ip!

Registration form abuse

web-1 [ssh] SSH Attack