| 37.49.230.126 |
attack |
"AmooT";tag=3533393765393339313363340132313832313335333935 |
2020-10-03 06:39:01 |
| 51.254.37.192 |
attackbots |
SSH Invalid Login |
2020-10-03 06:44:23 |
| 61.133.232.253 |
attackbotsspam |
Oct 3 00:05:17 *hidden* sshd[29098]: Failed password for invalid user nexus from 61.133.232.253 port 46546 ssh2 Oct 3 00:11:42 *hidden* sshd[32012]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.253 user=nginx Oct 3 00:11:43 *hidden* sshd[32012]: Failed password for *hidden* from 61.133.232.253 port 56062 ssh2 |
2020-10-03 06:54:41 |
| 47.113.87.53 |
attackspambots |
Unauthorized admin access - /admin/login.php |
2020-10-03 07:16:29 |
| 182.126.87.169 |
attack |
DATE:2020-10-02 22:38:55, IP:182.126.87.169, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq) |
2020-10-03 07:04:32 |
| 190.163.7.156 |
attackspambots |
C1,WP GET /wp-login.php |
2020-10-03 06:42:06 |
| 191.23.113.164 |
attackbotsspam |
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 07:17:37 |
| 190.167.244.87 |
attack |
Lines containing failures of 190.167.244.87
Oct 2 22:27:15 shared04 sshd[2191]: Did not receive identification string from 190.167.244.87 port 3192
Oct 2 22:27:17 shared04 sshd[2195]: Invalid user user1 from 190.167.244.87 port 3994
Oct 2 22:27:17 shared04 sshd[2195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.167.244.87
Oct 2 22:27:19 shared04 sshd[2195]: Failed password for invalid user user1 from 190.167.244.87 port 3994 ssh2
Oct 2 22:27:20 shared04 sshd[2195]: Connection closed by invalid user user1 190.167.244.87 port 3994 [preauth]
........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=190.167.244.87 |
2020-10-03 06:59:52 |
| 5.200.241.104 |
attackspam |
1601671289 - 10/02/2020 22:41:29 Host: 5.200.241.104/5.200.241.104 Port: 445 TCP Blocked |
2020-10-03 07:04:10 |
| 182.127.168.149 |
attack |
Auto Detect Rule!
proto TCP (SYN), 182.127.168.149:19191->gjan.info:23, len 40 |
2020-10-03 06:40:37 |
| 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 |
| 40.77.167.237 |
attack |
caw-Joomla User : try to access forms... |
2020-10-03 06:44:43 |
| 84.208.227.60 |
attack |
Invalid user mininet from 84.208.227.60 port 58162 |
2020-10-03 07:03:15 |
| 119.45.46.159 |
attack |
Oct 3 00:00:36 vpn01 sshd[11557]: Failed password for root from 119.45.46.159 port 48192 ssh2
... |
2020-10-03 07:01:33 |
| 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 |