| 34.120.202.146 |
attackbots |
RU spamvertising, health fraud - From: GlucaFIX
UBE 185.176.220.179 (EHLO gopxk.imkeeperr.com) 2 Cloud Ltd.
Spam link redfloppy.com = 185.246.116.174 Vpsville LLC – phishing redirect:
a) aptrk13.com = 35.204.93.160 Google
b) www.ep20trk.com = 34.120.202.146 Google
c) www.glucafix.us = 104.27.187.98, 104.27.186.98, 172.67.201.182 Cloudflare
d) glucafix.us = ditto
Images -
- http://redfloppy.com/web/imgs/mi1tb6fg.png = dailybetterhealth.com = 104.27.138.27, 104.27.139.27, 172.67.218.161 Cloudflare
- http://redfloppy.com/web/imgs/24sc48jt.png = unsub; no entity/address |
2020-10-03 12:06:19 |
| 191.23.113.164 |
attackbots |
Oct 2 22:34:06 mx01 sshd[15750]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 2 22:34:06 mx01 sshd[15750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r
Oct 2 22:34:08 mx01 sshd[15750]: Failed password for r.r from 191.23.113.164 port 53720 ssh2
Oct 2 22:34:08 mx01 sshd[15750]: Received disconnect from 191.23.113.164: 11: Bye Bye [preauth]
Oct 2 22:34:10 mx01 sshd[15754]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 2 22:34:11 mx01 sshd[15754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r
Oct 2 22:34:12 mx01 sshd[15754]: Failed password for r.r from 191.23.113.164 port 53804 ssh2
Oct 2 22:34:12 mx01 sshd[15754]: Received disconnect from 191.23.113.1........
------------------------------- |
2020-10-03 12:34:28 |
| 51.254.37.192 |
attack |
SSH Invalid Login |
2020-10-03 12:02:16 |
| 167.172.36.232 |
attack |
Oct 2 21:28:00 email sshd\[633\]: Invalid user unifi from 167.172.36.232
Oct 2 21:28:00 email sshd\[633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.36.232
Oct 2 21:28:01 email sshd\[633\]: Failed password for invalid user unifi from 167.172.36.232 port 46238 ssh2
Oct 2 21:31:17 email sshd\[1223\]: Invalid user walter from 167.172.36.232
Oct 2 21:31:17 email sshd\[1223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.36.232
... |
2020-10-03 12:10:22 |
| 51.254.32.102 |
attack |
Time: Sat Oct 3 04:12:50 2020 +0000
IP: 51.254.32.102 (FR/France/102.ip-51-254-32.eu)
Failures: 5 (sshd)
Interval: 3600 seconds
Blocked: Permanent Block [LF_SSHD]
Log entries:
Oct 3 04:04:42 48-1 sshd[84018]: Invalid user jenkins from 51.254.32.102 port 43994
Oct 3 04:04:44 48-1 sshd[84018]: Failed password for invalid user jenkins from 51.254.32.102 port 43994 ssh2
Oct 3 04:09:08 48-1 sshd[84139]: Invalid user vanessa from 51.254.32.102 port 55642
Oct 3 04:09:10 48-1 sshd[84139]: Failed password for invalid user vanessa from 51.254.32.102 port 55642 ssh2
Oct 3 04:12:49 48-1 sshd[84274]: Failed password for root from 51.254.32.102 port 33520 ssh2 |
2020-10-03 12:32:05 |
| 131.196.216.39 |
attackspam |
20 attempts against mh-ssh on star |
2020-10-03 12:11:51 |
| 154.209.253.241 |
attack |
fail2ban |
2020-10-03 12:29:08 |
| 52.191.166.171 |
attackbotsspam |
Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Invalid user ftpuser1 from 52.191.166.171
Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171
Oct 2 21:41:38 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Failed password for invalid user ftpuser1 from 52.191.166.171 port 36892 ssh2
Oct 2 22:41:04 Ubuntu-1404-trusty-64-minimal sshd\[619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 user=git
Oct 2 22:41:06 Ubuntu-1404-trusty-64-minimal sshd\[619\]: Failed password for git from 52.191.166.171 port 60674 ssh2 |
2020-10-03 07:20:35 |
| 46.101.5.144 |
attack |
20 attempts against mh-ssh on soil |
2020-10-03 07:21:27 |
| 1.255.48.197 |
attack |
(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-03 12:17:46 |
| 34.96.218.228 |
attackspam |
4 SSH login attempts. |
2020-10-03 12:28:10 |
| 45.148.121.92 |
attackspam |
45.148.121.92 was recorded 5 times by 4 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 11, 60 |
2020-10-03 12:12:41 |
| 193.112.191.228 |
attack |
Automatic Fail2ban report - Trying login SSH |
2020-10-03 12:31:32 |
| 157.230.245.91 |
attackspambots |
Failed password for invalid user kost from 157.230.245.91 port 46704 ssh2 |
2020-10-03 12:27:20 |
| 89.233.112.6 |
attackbots |
port scan and connect, tcp 23 (telnet) |
2020-10-03 12:13:36 |