Brute force attack attempt

Attempted to connect 3 times to port 3389 TCP

[MK-Root1] Blocked by UFW

Nov 22 00:21:08 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 22 00:21:23 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 22 00:23:23 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=<7TRHleOXsF9drl0F>
Nov 22 00:24:05 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 22 00:24:10 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=<3cfcl+OXeupdrl0F
...

Nov 21 07:20:55 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 21 07:21:23 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 21 07:24:53 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=<3pTaWtWXmuJdrl0F>
Nov 21 07:25:22 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov 21 07:28:09 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session
...

Nov  8 05:50:14 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov  8 05:51:04 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov  8 05:53:32 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov  8 05:53:49 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
Nov  8 05:54:14 host3 dovecot: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
...

2019-11-07T09:19:36.413553host3.slimhost.com.ua dovecot[859034]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=<+7RPU72WXjBdrl0F>
2019-11-07T09:22:11.104250host3.slimhost.com.ua dovecot[859034]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
2019-11-07T09:23:22.392802host3.slimhost.com.ua dovecot[859034]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=<4oHIYL2WgIJdrl0F>
2019-11-07T09:23:50.474822host3.slimhost.com.ua dovecot[859034]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=93.174.93.5, lip=207.180.241.50, session=
2019-11-07T09:24:09.190135host3.slimhost.com.ua dovecot[8590
...

Nov  4 18:42:40 h1655903 dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.174.93.5, lip=85.214.28.7, session=\<6SZ214iWuGpdrl0F\>
Nov  4 21:11:54 h1655903 dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.174.93.5, lip=85.214.28.7, session=\
Nov  4 23:41:25 h1655903 dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.174.93.5, lip=85.214.28.7, session=\
...

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

10/25/2019-18:16:32.565002 93.174.93.5 Protocol: 6 ET DROP Dshield Block Listed Source group 1

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

Exceeded maximum number of incorrect SMTP login attempts

Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:32:27 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: hostname no-reveeclipse-dns-configured.com does not resolve to address 93.174.93.5
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: connect from unknown[93.174.93.5]
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: warning: unknown[93.174.93.5]: SASL LOGIN authentication failed: authentication failure
Oct 23 17:33:22 nirvana postfix/smtpd[15274]: disconnect from unknown[93.174.93.5]
Oct 23 17:40:27 nirvana postfix/smtpd[15903]: warning: hostname no-reveeclipse-dns-configured.com does not resolve........
-------------------------------

RDPBruteFlS24

Probing wordpress site

GET /phpMyAdmin/scripts/setup.php HTTP/1.1
GET /phpmyadmin/scripts/setup.php HTTP/1.1
GET /myadmin/scripts/setup.php HTTP/1.1
GET /MyAdmin/scripts/setup.php HTTP/1.1
GET /w00tw00t.at.blackhats.romanian.anti-sec:) HTTP/1.1
GET /pma/scripts/setup.php HTTP/1.1

nginx botsearch

93.174.93.195 was recorded 5 times by 4 hosts attempting to connect to the following ports: 10011,10015. Incident counter (4h, 24h, all-time): 5, 26, 14519

ET CINS Active Threat Intelligence Poor Reputation IP group 81 - port: 10003 proto: udp cat: Misc Attackbytes: 71

ET CINS Active Threat Intelligence Poor Reputation IP group 82 - port: 7681 proto: udp cat: Misc Attackbytes: 71

93.174.93.195 was recorded 7 times by 4 hosts attempting to connect to the following ports: 7168,6999. Incident counter (4h, 24h, all-time): 7, 48, 14441

Brute force blocker - service: dovecot1 - aantal: 25 - Mon Sep  3 10:50:12 2018

Brute force blocker - service: dovecot1 - aantal: 25 - Mon Sep  3 10:50:12 2018

Brute force blocker - service: dovecot1 - aantal: 25 - Mon Sep  3 10:50:12 2018

93.174.93.195 was recorded 7 times by 4 hosts attempting to connect to the following ports: 2304,2306,2305. Incident counter (4h, 24h, all-time): 7, 31, 14296

[H1.VM1] Blocked by UFW

[MK-VM5] Blocked by UFW

Port scan on 24 port(s): 74 165 323 358 382 427 529 530 643 684 703 709 754 773 776 791 838 845 874 887 917 980 993 1000

$f2bV_matches

20/2/13@23:55:45: FAIL: Alarm-SSH address from=125.25.197.242
...

Honeypot attack, port: 445, PTR: localhost.

(From eric@talkwithcustomer.com) Hello bowerschiro.net,

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 bowerschiro.net.
- 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 bowerschiro.net, 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 famous marketer

Invalid user fake from 104.244.79.250 port 34306

Feb 14 07:46:42 silence02 sshd[13281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.250.50
Feb 14 07:46:44 silence02 sshd[13281]: Failed password for invalid user adrock from 212.47.250.50 port 34072 ssh2
Feb 14 07:56:34 silence02 sshd[13824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.250.50

xmlrpc attack

Feb 14 08:24:29 h1745522 sshd[19687]: Invalid user 123456 from 142.112.87.158 port 42654
Feb 14 08:24:29 h1745522 sshd[19687]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.112.87.158
Feb 14 08:24:29 h1745522 sshd[19687]: Invalid user 123456 from 142.112.87.158 port 42654
Feb 14 08:24:31 h1745522 sshd[19687]: Failed password for invalid user 123456 from 142.112.87.158 port 42654 ssh2
Feb 14 08:29:12 h1745522 sshd[19806]: Invalid user zcadqe from 142.112.87.158 port 56712
Feb 14 08:29:12 h1745522 sshd[19806]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.112.87.158
Feb 14 08:29:12 h1745522 sshd[19806]: Invalid user zcadqe from 142.112.87.158 port 56712
Feb 14 08:29:14 h1745522 sshd[19806]: Failed password for invalid user zcadqe from 142.112.87.158 port 56712 ssh2
Feb 14 08:34:11 h1745522 sshd[19899]: Invalid user apacheds from 142.112.87.158 port 54108
...

Feb 14 09:47:00 ncomp sshd[24271]: Invalid user tony_george from 51.89.166.45
Feb 14 09:47:00 ncomp sshd[24271]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.166.45
Feb 14 09:47:00 ncomp sshd[24271]: Invalid user tony_george from 51.89.166.45
Feb 14 09:47:02 ncomp sshd[24271]: Failed password for invalid user tony_george from 51.89.166.45 port 42340 ssh2

Honeypot attack, port: 81, PTR: 177.157.97.139.dynamic.adsl.gvt.net.br.

Attempt to attack host OS, exploiting network vulnerabilities, on 14-02-2020 04:55:08.

1581656120 - 02/14/2020 05:55:20 Host: 36.68.168.193/36.68.168.193 Port: 445 TCP Blocked

Brute force attempt

Feb 14 05:39:01 ns382633 sshd\[17543\]: Invalid user admin from 77.221.146.47 port 58114
Feb 14 05:39:01 ns382633 sshd\[17543\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.221.146.47
Feb 14 05:39:03 ns382633 sshd\[17543\]: Failed password for invalid user admin from 77.221.146.47 port 58114 ssh2
Feb 14 05:55:46 ns382633 sshd\[20592\]: Invalid user server from 77.221.146.47 port 39054
Feb 14 05:55:46 ns382633 sshd\[20592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.221.146.47

(From eric@talkwithcustomer.com) Hello bowerschiro.net,

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 bowerschiro.net.
- 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 bowerschiro.net, 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 famous marketer

2001:DB8:0:0:8:800:200C:417A