Mail sent to address harvested from blog legal page

Feb 18 13:22:07 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:14 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:16 system,error,critical: login failure for user Administrator from 59.126.123.192 via telnet
Feb 18 13:22:21 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:27 system,error,critical: login failure for user guest from 59.126.123.192 via telnet
Feb 18 13:22:29 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:35 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:44 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:46 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:48 system,error,critical: login failure for user admin from 59.126.123.192 via telnet

Mail sent to address hacked/leaked from Gamigo

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

Automatic report - Port Scan Attack

1582032179 - 02/18/2020 14:22:59 Host: 42.114.204.18/42.114.204.18 Port: 445 TCP Blocked

Honeypot hit: misc

Brute force attempt

Feb 18 14:50:42 vps46666688 sshd[4127]: Failed password for root from 129.242.219.106 port 56254 ssh2
...

Feb 18 18:17:12 grey postfix/smtpd\[31966\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.160\]: 554 5.7.1 Service unavailable\; Client host \[185.143.223.160\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[185.143.223.160\]\; from=\ to=\ proto=ESMTP helo=\<\[185.143.223.163\]\>Feb 18 18:17:12 grey postfix/smtpd\[31966\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.160\]: 554 5.7.1 Service unavailable\; Client host \[185.143.223.160\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[185.143.223.160\]\; from=\ to=\ proto=ESMTP helo=\<\[185.143.223.163\]\>Feb 18 18:17:12 grey postfix/smtpd\[31966\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.160\]: 554 5.7.1 Service unavailable\; Client host \[185.143.223.160\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[185.143.223.160\]\; from=\ to=\

Wordpress Admin Login attack

Feb 18 17:30:07 sd-53420 sshd\[19242\]: Invalid user qwertyuiop from 211.51.62.226
Feb 18 17:30:07 sd-53420 sshd\[19242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.51.62.226
Feb 18 17:30:09 sd-53420 sshd\[19242\]: Failed password for invalid user qwertyuiop from 211.51.62.226 port 36268 ssh2
Feb 18 17:33:23 sd-53420 sshd\[19520\]: Invalid user nmrihserver123 from 211.51.62.226
Feb 18 17:33:23 sd-53420 sshd\[19520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.51.62.226
...

Feb 18 18:48:05 MK-Soft-Root2 sshd[3146]: Failed password for root from 106.54.114.208 port 51894 ssh2
Feb 18 18:51:25 MK-Soft-Root2 sshd[3912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.114.208 
...

Feb 18 14:23:00 lnxweb61 sshd[25626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.152.29.204
Feb 18 14:23:00 lnxweb61 sshd[25628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.152.29.204
Feb 18 14:23:03 lnxweb61 sshd[25626]: Failed password for invalid user pi from 88.152.29.204 port 42738 ssh2
Feb 18 14:23:03 lnxweb61 sshd[25628]: Failed password for invalid user pi from 88.152.29.204 port 42742 ssh2

$f2bV_matches