| 167.172.25.74 |
attackspam |
no |
2020-10-03 19:45:14 |
| 66.70.189.203 |
attackspam |
$f2bV_matches |
2020-10-03 20:09:46 |
| 51.89.148.69 |
attackbotsspam |
Invalid user guest1 from 51.89.148.69 port 57754 |
2020-10-03 19:41:03 |
| 42.200.148.195 |
attack |
TCP (SYN) 42.200.148.195:10932 -> port 23, len 44 |
2020-10-03 19:58:58 |
| 63.80.187.59 |
attackbots |
E-Mail Spam (RBL) [REJECTED] |
2020-10-03 19:37:35 |
| 46.187.38.244 |
attackbots |
TCP (SYN) 46.187.38.244:47144 -> port 1080, len 60 |
2020-10-03 19:53:34 |
| 210.242.52.28 |
attackspam |
(sshd) Failed SSH login from 210.242.52.28 (TW/Taiwan/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 3 07:42:08 server2 sshd[17003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.242.52.28 user=mysql
Oct 3 07:42:11 server2 sshd[17003]: Failed password for mysql from 210.242.52.28 port 59731 ssh2
Oct 3 07:50:25 server2 sshd[18350]: Invalid user ubuntu from 210.242.52.28 port 33464
Oct 3 07:50:27 server2 sshd[18350]: Failed password for invalid user ubuntu from 210.242.52.28 port 33464 ssh2
Oct 3 07:52:23 server2 sshd[18683]: Invalid user deploy from 210.242.52.28 port 3517 |
2020-10-03 19:28:26 |
| 94.102.56.238 |
attackbots |
2020-10-03 13:06:53 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:06:59 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:07:09 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:07:26 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:07:43 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:08:00 dovecot_login authenticator failed for \(User\) \[94.102.56.238\]: 535 Incorrect authentication data \(set_id=info@no-server.de\)
2020-10-03 13:08:00 SMTP call from \(User\) \[94.102.56.238\] dropped: too many nonmail commands \(l
... |
2020-10-03 20:01:35 |
| 103.84.175.197 |
attackbotsspam |
CMS (WordPress or Joomla) login attempt. |
2020-10-03 19:58:12 |
| 51.83.69.142 |
attackspam |
Oct 3 11:22:47 ip106 sshd[29187]: Failed password for root from 51.83.69.142 port 32798 ssh2
... |
2020-10-03 19:44:08 |
| 207.244.252.113 |
attackspambots |
(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 20:02:21 |
| 51.77.66.35 |
attackspam |
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-10-03T10:15:22Z and 2020-10-03T11:15:42Z |
2020-10-03 19:52:43 |
| 162.142.125.50 |
attack |
[Sat Oct 03 17:47:25.195961 2020] [:error] [pid 10959:tid 140392171284224] [client 162.142.125.50:38322] [client 162.142.125.50] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/coreruleset-3.3.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "756"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197:80"] [severity "WARNING"] [ver "OWASP_CRS/3.3.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "X3hWveXmh9WfvxChEP5EpgAAAGA"]
... |
2020-10-03 19:30:06 |
| 165.21.103.192 |
attackspambots |
SSH login attempts. |
2020-10-03 19:27:09 |
| 206.189.136.185 |
attackbots |
Oct 3 05:55:19 ws19vmsma01 sshd[58825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.136.185
Oct 3 05:55:21 ws19vmsma01 sshd[58825]: Failed password for invalid user kk from 206.189.136.185 port 47484 ssh2
... |
2020-10-03 19:28:41 |