| 139.99.203.12 |
attackspambots |
(sshd) Failed SSH login from 139.99.203.12 (AU/Australia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 4 15:51:41 server4 sshd[23678]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.203.12 user=root
Sep 4 15:51:43 server4 sshd[23678]: Failed password for root from 139.99.203.12 port 51122 ssh2
Sep 4 15:58:58 server4 sshd[28369]: Invalid user bitnami from 139.99.203.12
Sep 4 15:58:58 server4 sshd[28369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.203.12
Sep 4 15:59:00 server4 sshd[28369]: Failed password for invalid user bitnami from 139.99.203.12 port 47564 ssh2 |
2020-09-05 07:23:26 |
| 172.107.95.30 |
attackspam |
Honeypot hit. |
2020-09-05 07:11:08 |
| 183.194.212.16 |
attackspambots |
Sep 4 23:40:39 vps sshd[20024]: Failed password for git from 183.194.212.16 port 48468 ssh2
Sep 4 23:55:53 vps sshd[20711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.194.212.16
Sep 4 23:55:55 vps sshd[20711]: Failed password for invalid user integra from 183.194.212.16 port 35680 ssh2
... |
2020-09-05 07:15:47 |
| 185.225.136.37 |
attackbots |
(From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this…
- Someone does a search and winds up at drlesliechiro.com.
- They hang out for a minute to check it out. “I’m interested… but… maybe…”
- And then they hit the back button and check out the other search results instead.
- Bottom line – you got an eyeball, but nothing else to show for it.
- There they go.
This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace.
But you CAN fix that.
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site.
CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works.
Time is money when it comes to connecting with leads – |
2020-09-05 07:09:31 |
| 190.38.27.203 |
attackspam |
Honeypot attack, port: 445, PTR: 190-38-27-203.dyn.dsl.cantv.net. |
2020-09-05 06:51:17 |
| 149.129.52.21 |
attackspambots |
149.129.52.21 - - [04/Sep/2020:11:26:05 -0600] "GET /wp-login.php HTTP/1.1" 301 468 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
... |
2020-09-05 06:55:06 |
| 192.241.200.105 |
attack |
firewall-block, port(s): 2323/tcp |
2020-09-05 07:23:05 |
| 23.108.46.226 |
attack |
(From eric@talkwithwebvisitor.com) Cool website!
My name’s Eric, and I just found your site - wellness-chiropractic-center.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
But if you don’t mind me asking – after someone like me stumbles across wellness-chiropractic-center.com, what usually happens?
Is your site generating leads for your business?
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.
Not good.
Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”
You can –
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know IMMEDIATELY – so that you can talk to that lead while they’r |
2020-09-05 07:16:43 |
| 222.186.175.151 |
attackbotsspam |
SSH brute-force attempt |
2020-09-05 07:05:38 |
| 112.85.42.173 |
attackbots |
Sep 5 00:40:07 sd-69548 sshd[755217]: Unable to negotiate with 112.85.42.173 port 23352: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
Sep 5 01:17:12 sd-69548 sshd[757731]: Unable to negotiate with 112.85.42.173 port 11297: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
... |
2020-09-05 07:20:41 |
| 42.106.200.255 |
attackbots |
Sep 4 18:51:00 mellenthin postfix/smtpd[29582]: NOQUEUE: reject: RCPT from unknown[42.106.200.255]: 554 5.7.1 Service unavailable; Client host [42.106.200.255] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/42.106.200.255; from= to= proto=ESMTP helo=<[49.32.55.180]> |
2020-09-05 06:58:19 |
| 82.115.213.204 |
attackspambots |
REQUESTED PAGE: /wp-json/contact-form-7/v1/contact-forms/382/feedback |
2020-09-05 07:01:08 |
| 45.141.87.5 |
attackbotsspam |
RDP brute forcing (d) |
2020-09-05 07:07:42 |
| 141.98.10.209 |
attack |
2020-09-04T23:19:57.024437shield sshd\[22092\]: Invalid user 1234 from 141.98.10.209 port 49980
2020-09-04T23:19:57.037605shield sshd\[22092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.209
2020-09-04T23:19:59.491901shield sshd\[22092\]: Failed password for invalid user 1234 from 141.98.10.209 port 49980 ssh2
2020-09-04T23:20:39.786556shield sshd\[22257\]: Invalid user user from 141.98.10.209 port 41124
2020-09-04T23:20:39.795474shield sshd\[22257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.209 |
2020-09-05 07:24:40 |
| 194.26.25.97 |
attack |
Multiport scan : 43 ports scanned 58 221 292 322 442 565 710 939 1876 1891 1901 2025 2552 2795 4894 5435 5671 6336 8990 9222 9351 9456 9585 9769 12124 13022 13135 13226 14145 14444 14725 18586 19495 19756 20726 21216 21439 22021 22227 24445 26914 31112 32122 |
2020-09-05 07:12:45 |