| 81.69.177.253 |
attackbotsspam |
SSH Invalid Login |
2020-10-03 06:49:58 |
| 139.155.91.141 |
attackspambots |
2020-10-02T22:35:38.294198shield sshd\[24953\]: Invalid user git from 139.155.91.141 port 38092
2020-10-02T22:35:38.303149shield sshd\[24953\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.91.141
2020-10-02T22:35:40.415755shield sshd\[24953\]: Failed password for invalid user git from 139.155.91.141 port 38092 ssh2
2020-10-02T22:40:28.378099shield sshd\[25266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.91.141 user=root
2020-10-02T22:40:30.972083shield sshd\[25266\]: Failed password for root from 139.155.91.141 port 36610 ssh2 |
2020-10-03 06:46:51 |
| 114.232.109.187 |
attack |
SSH Invalid Login |
2020-10-03 06:38:00 |
| 211.220.27.191 |
attackbotsspam |
Invalid user jboss from 211.220.27.191 port 55634 |
2020-10-03 06:56:03 |
| 195.54.167.152 |
attackbots |
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-10-02T21:49:57Z and 2020-10-02T22:32:42Z |
2020-10-03 06:57:25 |
| 212.179.226.196 |
attackspambots |
2020-10-02T11:58:56.645254paragon sshd[585643]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.179.226.196
2020-10-02T11:58:56.641305paragon sshd[585643]: Invalid user admin from 212.179.226.196 port 37736
2020-10-02T11:58:59.422801paragon sshd[585643]: Failed password for invalid user admin from 212.179.226.196 port 37736 ssh2
2020-10-02T12:03:44.634055paragon sshd[585723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.179.226.196 user=root
2020-10-02T12:03:47.280279paragon sshd[585723]: Failed password for root from 212.179.226.196 port 46044 ssh2
... |
2020-10-03 06:28:50 |
| 123.30.149.76 |
attackbots |
$f2bV_matches |
2020-10-03 06:49:02 |
| 41.207.7.240 |
attackbotsspam |
Lines containing failures of 41.207.7.240
Oct 2 22:24:45 new sshd[31337]: Did not receive identification string from 41.207.7.240 port 57604
Oct 2 22:24:45 new sshd[31338]: Did not receive identification string from 41.207.7.240 port 57607
Oct 2 22:24:48 new sshd[31341]: Did not receive identification string from 41.207.7.240 port 57651
Oct 2 22:24:48 new sshd[31339]: Invalid user dircreate from 41.207.7.240 port 57884
Oct 2 22:24:48 new sshd[31339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240
Oct 2 22:24:50 new sshd[31339]: Failed password for invalid user dircreate from 41.207.7.240 port 57884 ssh2
Oct 2 22:24:50 new sshd[31343]: Invalid user dircreate from 41.207.7.240 port 57893
Oct 2 22:24:50 new sshd[31343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240
Oct 2 22:24:50 new sshd[31339]: Connection closed by invalid user dircreate 41.207.7.240 port ........
------------------------------ |
2020-10-03 06:49:34 |
| 188.131.131.59 |
attackspam |
SSH bruteforce |
2020-10-03 06:51:04 |
| 59.127.107.1 |
attack |
TCP (SYN) 59.127.107.1:5292 -> port 23, len 40 |
2020-10-03 06:28:26 |
| 83.239.38.2 |
attackbots |
Oct 2 22:05:50 vlre-nyc-1 sshd\[10981\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.239.38.2 user=root
Oct 2 22:05:52 vlre-nyc-1 sshd\[10981\]: Failed password for root from 83.239.38.2 port 42316 ssh2
Oct 2 22:08:32 vlre-nyc-1 sshd\[11051\]: Invalid user dcadmin from 83.239.38.2
Oct 2 22:08:32 vlre-nyc-1 sshd\[11051\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.239.38.2
Oct 2 22:08:34 vlre-nyc-1 sshd\[11051\]: Failed password for invalid user dcadmin from 83.239.38.2 port 60788 ssh2
... |
2020-10-03 07:00:47 |
| 89.233.112.6 |
attackspambots |
port scan and connect, tcp 23 (telnet) |
2020-10-03 06:55:38 |
| 140.143.127.36 |
attackspambots |
Oct 2 21:39:46 sshd\[15398\]: Invalid user andrei from 140.143.127.36Oct 2 21:39:47 sshd\[15398\]: Failed password for invalid user andrei from 140.143.127.36 port 38994 ssh2
... |
2020-10-03 06:30:53 |
| 193.169.252.37 |
attack |
PHI,WP GET /wp-login.php
GET //wp-login.php |
2020-10-03 06:47:25 |
| 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 |