| 139.59.161.78 |
attack |
Oct 2 22:59:28 DAAP sshd[3444]: Invalid user x from 139.59.161.78 port 12865
Oct 2 22:59:28 DAAP sshd[3444]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.161.78
Oct 2 22:59:28 DAAP sshd[3444]: Invalid user x from 139.59.161.78 port 12865
Oct 2 22:59:30 DAAP sshd[3444]: Failed password for invalid user x from 139.59.161.78 port 12865 ssh2
Oct 2 23:04:06 DAAP sshd[3524]: Invalid user deployer from 139.59.161.78 port 36970
... |
2020-10-03 06:47:52 |
| 114.232.109.187 |
attack |
SSH Invalid Login |
2020-10-03 06:38:00 |
| 15.236.144.21 |
attack |
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: ec2-15-236-144-21.eu-west-3.compute.amazonaws.com. |
2020-10-03 06:22:19 |
| 165.232.40.228 |
attackspam |
Oct 1 21:06:09 plex-server sshd[1823782]: Failed password for invalid user magento from 165.232.40.228 port 54234 ssh2
Oct 1 21:10:01 plex-server sshd[1825432]: Invalid user jboss from 165.232.40.228 port 38248
Oct 1 21:10:01 plex-server sshd[1825432]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.232.40.228
Oct 1 21:10:01 plex-server sshd[1825432]: Invalid user jboss from 165.232.40.228 port 38248
Oct 1 21:10:03 plex-server sshd[1825432]: Failed password for invalid user jboss from 165.232.40.228 port 38248 ssh2
... |
2020-10-03 06:33:30 |
| 209.141.35.79 |
attackbotsspam |
scans 2 times in preceeding hours on the ports (in chronological order) 11211 1900 |
2020-10-03 06:32:59 |
| 59.48.174.6 |
attack |
1433/tcp 1433/tcp 1433/tcp...
[2020-08-11/10-01]4pkt,1pt.(tcp) |
2020-10-03 06:34:08 |
| 212.95.213.194 |
attackspambots |
23/tcp 23/tcp
[2020-08-15/10-01]2pkt |
2020-10-03 06:34:35 |
| 95.133.161.54 |
attackspambots |
445/tcp 445/tcp 445/tcp
[2020-09-15/10-01]3pkt |
2020-10-03 06:23:43 |
| 121.201.124.41 |
attackspambots |
port scan and connect, tcp 1433 (ms-sql-s) |
2020-10-03 06:38:39 |
| 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 06:58:51 |
| 45.79.85.237 |
attackbotsspam |
2252/tcp 4592/tcp 2727/tcp...
[2020-09-15/10-02]5pkt,5pt.(tcp) |
2020-10-03 06:23:56 |
| 81.18.134.18 |
attack |
Unauthorised access (Oct 2) SRC=81.18.134.18 LEN=52 TTL=118 ID=15089 DF TCP DPT=445 WINDOW=8192 SYN |
2020-10-03 06:36:03 |
| 27.151.115.81 |
attackspam |
port scan and connect, tcp 1433 (ms-sql-s) |
2020-10-03 06:55:49 |
| 81.68.230.85 |
attackspambots |
UDP 81.68.230.85:47572 -> port 27015, len 53 |
2020-10-03 06:29:36 |
| 34.120.202.146 |
attack |
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 06:48:21 |