| 45.142.120.39 |
attackspambots |
Oct 3 21:53:41 relay postfix/smtpd\[15760\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 21:53:56 relay postfix/smtpd\[14135\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 21:53:59 relay postfix/smtpd\[14088\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 21:54:01 relay postfix/smtpd\[14150\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 21:54:18 relay postfix/smtpd\[14150\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 21:54:18 relay postfix/smtpd\[16681\]: warning: unknown\[45.142.120.39\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
... |
2020-10-04 04:03:18 |
| 122.51.194.254 |
attackbotsspam |
Oct 3 20:38:44 nextcloud sshd\[11664\]: Invalid user cmsuser from 122.51.194.254
Oct 3 20:38:44 nextcloud sshd\[11664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.194.254
Oct 3 20:38:46 nextcloud sshd\[11664\]: Failed password for invalid user cmsuser from 122.51.194.254 port 43060 ssh2 |
2020-10-04 03:59:24 |
| 218.104.225.140 |
attack |
2020-10-03T19:39:58.207727shield sshd\[10779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.225.140 user=root
2020-10-03T19:39:59.908857shield sshd\[10779\]: Failed password for root from 218.104.225.140 port 53356 ssh2
2020-10-03T19:43:31.371453shield sshd\[11306\]: Invalid user support from 218.104.225.140 port 32797
2020-10-03T19:43:31.381064shield sshd\[11306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.225.140
2020-10-03T19:43:33.659824shield sshd\[11306\]: Failed password for invalid user support from 218.104.225.140 port 32797 ssh2 |
2020-10-04 03:57:29 |
| 120.9.254.171 |
attack |
Port Scan detected!
... |
2020-10-04 04:25:20 |
| 138.68.148.177 |
attack |
DATE:2020-10-03 20:05:08, IP:138.68.148.177, PORT:ssh SSH brute force auth (docker-dc) |
2020-10-04 04:04:27 |
| 178.80.54.189 |
attackspambots |
178.80.54.189 - - [02/Oct/2020:22:37:21 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
178.80.54.189 - - [02/Oct/2020:22:37:22 +0100] "POST /wp-login.php HTTP/1.1" 200 7644 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
178.80.54.189 - - [02/Oct/2020:22:38:22 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
... |
2020-10-04 03:48:29 |
| 122.51.31.40 |
attack |
SSH brutforce |
2020-10-04 04:14:44 |
| 103.142.34.34 |
attackspam |
SSH brutforce |
2020-10-04 03:58:18 |
| 111.231.193.72 |
attackbots |
(sshd) Failed SSH login from 111.231.193.72 (CN/China/-): 5 in the last 3600 secs |
2020-10-04 04:15:09 |
| 66.70.189.203 |
attackbotsspam |
Oct 3 19:50:09 buvik sshd[29772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.189.203
Oct 3 19:50:11 buvik sshd[29772]: Failed password for invalid user alex from 66.70.189.203 port 48254 ssh2
Oct 3 19:57:52 buvik sshd[30713]: Invalid user nikhil from 66.70.189.203
... |
2020-10-04 04:07:14 |
| 51.255.28.53 |
attackspambots |
Invalid user rust from 51.255.28.53 port 55490 |
2020-10-04 04:11:13 |
| 108.62.123.167 |
attackspam |
[2020-10-03 16:11:31] NOTICE[1182] chan_sip.c: Registration from '"8000" ' failed for '108.62.123.167:5624' - Wrong password
[2020-10-03 16:11:31] SECURITY[1204] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2020-10-03T16:11:31.635-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="8000",SessionID="0x7f22f8418138",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/108.62.123.167/5624",Challenge="15bef515",ReceivedChallenge="15bef515",ReceivedHash="512e4bc3cd8b191cc5e7347adff29ca6"
[2020-10-03 16:11:31] NOTICE[1182] chan_sip.c: Registration from '"8000" ' failed for '108.62.123.167:5624' - Wrong password
[2020-10-03 16:11:31] SECURITY[1204] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2020-10-03T16:11:31.818-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="8000",SessionID="0x7f22f83b6678",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP
... |
2020-10-04 04:23:03 |
| 222.67.231.1 |
attackspambots |
2020-10-02T20:29:21.719851abusebot-8.cloudsearch.cf sshd[24509]: Invalid user kvm from 222.67.231.1 port 48790
2020-10-02T20:29:21.726446abusebot-8.cloudsearch.cf sshd[24509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.67.231.1
2020-10-02T20:29:21.719851abusebot-8.cloudsearch.cf sshd[24509]: Invalid user kvm from 222.67.231.1 port 48790
2020-10-02T20:29:24.315564abusebot-8.cloudsearch.cf sshd[24509]: Failed password for invalid user kvm from 222.67.231.1 port 48790 ssh2
2020-10-02T20:33:05.440009abusebot-8.cloudsearch.cf sshd[24652]: Invalid user admin from 222.67.231.1 port 53302
2020-10-02T20:33:05.449433abusebot-8.cloudsearch.cf sshd[24652]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.67.231.1
2020-10-02T20:33:05.440009abusebot-8.cloudsearch.cf sshd[24652]: Invalid user admin from 222.67.231.1 port 53302
2020-10-02T20:33:07.457229abusebot-8.cloudsearch.cf sshd[24652]: Failed password for
... |
2020-10-04 04:09:49 |
| 223.99.203.186 |
attackbotsspam |
Automatic report - Banned IP Access |
2020-10-04 04:10:47 |
| 207.244.252.113 |
attackspam |
(From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call.
$24.99/mo Flat Fee Credit Card Processing (Unlimited)
1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware?
New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019.
Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees.
2) You're legally able to demand this new option.
Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options?
We repre |
2020-10-04 04:00:38 |