City: unknown
Region: unknown
Country: United States of America
Internet Service Provider: DigitalOcean LLC
Hostname: unknown
Organization: unknown
Usage Type: Data Center/Web Hosting/Transit
| Type | Details | Datetime |
|---|---|---|
| attackspambots | (sshd) Failed SSH login from 138.68.50.78 (US/United States/-): 5 in the last 3600 secs |
2020-10-12 04:12:44 |
| attack | Oct 11 12:26:48 server sshd[4930]: Failed password for invalid user new from 138.68.50.78 port 52160 ssh2 Oct 11 12:30:19 server sshd[6901]: Failed password for root from 138.68.50.78 port 58464 ssh2 Oct 11 12:33:58 server sshd[8755]: Failed password for invalid user apache from 138.68.50.78 port 36560 ssh2 |
2020-10-11 20:11:56 |
| attack | Oct 11 06:13:19 root sshd[27400]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.78 user=root Oct 11 06:13:21 root sshd[27400]: Failed password for root from 138.68.50.78 port 33222 ssh2 ... |
2020-10-11 12:10:50 |
| attackbotsspam | SSH Brute Force |
2020-10-11 05:34:25 |
| IP | Type | Details | Datetime |
|---|---|---|---|
| 138.68.50.18 | attack | Exploited Host. |
2020-07-26 02:43:14 |
| 138.68.50.18 | attackbots | Jun 19 15:38:55 vps687878 sshd\[20915\]: Failed password for invalid user testftp from 138.68.50.18 port 52366 ssh2 Jun 19 15:40:42 vps687878 sshd\[21173\]: Invalid user developer from 138.68.50.18 port 43972 Jun 19 15:40:42 vps687878 sshd\[21173\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Jun 19 15:40:44 vps687878 sshd\[21173\]: Failed password for invalid user developer from 138.68.50.18 port 43972 ssh2 Jun 19 15:42:32 vps687878 sshd\[21506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 user=root ... |
2020-06-19 22:05:17 |
| 138.68.50.18 | attackbots | Jun 15 03:52:34 ws26vmsma01 sshd[91294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Jun 15 03:52:36 ws26vmsma01 sshd[91294]: Failed password for invalid user gateway from 138.68.50.18 port 39384 ssh2 ... |
2020-06-15 15:54:57 |
| 138.68.50.18 | attackbots | Jun 13 23:03:10 vps sshd[899884]: Failed password for invalid user mmadmin from 138.68.50.18 port 39616 ssh2 Jun 13 23:04:09 vps sshd[903541]: Invalid user Welkome$#1234 from 138.68.50.18 port 49994 Jun 13 23:04:09 vps sshd[903541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Jun 13 23:04:11 vps sshd[903541]: Failed password for invalid user Welkome$#1234 from 138.68.50.18 port 49994 ssh2 Jun 13 23:05:09 vps sshd[911289]: Invalid user meres from 138.68.50.18 port 60372 ... |
2020-06-14 09:19:01 |
| 138.68.50.18 | attack | May 24 12:12:24 ns3033917 sshd[29082]: Failed password for root from 138.68.50.18 port 38006 ssh2 May 24 12:13:44 ns3033917 sshd[29088]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 user=root May 24 12:13:46 ns3033917 sshd[29088]: Failed password for root from 138.68.50.18 port 53416 ssh2 ... |
2020-05-24 22:48:00 |
| 138.68.50.18 | attackbotsspam | Invalid user training from 138.68.50.18 port 44196 |
2020-05-16 13:18:10 |
| 138.68.50.18 | attackbots | This client attempted to login to an administrator account on a Website, or abused from another resource. |
2020-04-16 14:21:51 |
| 138.68.50.18 | attackspambots | $f2bV_matches |
2020-04-13 12:43:28 |
| 138.68.50.18 | attack | 2020-03-09 UTC: (2x) - miyazawa,nproc |
2020-03-10 21:31:21 |
| 138.68.50.18 | attackbots | Mar 9 18:40:18 areeb-Workstation sshd[26509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Mar 9 18:40:19 areeb-Workstation sshd[26509]: Failed password for invalid user miyazawa from 138.68.50.18 port 42038 ssh2 ... |
2020-03-09 22:27:55 |
| 138.68.50.18 | attackspam | Feb 14 19:43:39 plusreed sshd[9310]: Invalid user close from 138.68.50.18 ... |
2020-02-15 09:07:11 |
| 138.68.50.1 | attack | web Attack on Wordpress site at 2020-01-02. |
2020-01-03 02:46:50 |
| 138.68.50.18 | attackbots | Dec 13 04:42:30 firewall sshd[5913]: Invalid user helyn from 138.68.50.18 Dec 13 04:42:32 firewall sshd[5913]: Failed password for invalid user helyn from 138.68.50.18 port 57118 ssh2 Dec 13 04:47:54 firewall sshd[6128]: Invalid user mrtg1 from 138.68.50.18 ... |
2019-12-13 15:48:41 |
| 138.68.50.18 | attackbotsspam | Dec 8 14:07:32 kapalua sshd\[5921\]: Invalid user ricchiardi from 138.68.50.18 Dec 8 14:07:32 kapalua sshd\[5921\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Dec 8 14:07:34 kapalua sshd\[5921\]: Failed password for invalid user ricchiardi from 138.68.50.18 port 45692 ssh2 Dec 8 14:12:56 kapalua sshd\[6691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 user=root Dec 8 14:12:58 kapalua sshd\[6691\]: Failed password for root from 138.68.50.18 port 54692 ssh2 |
2019-12-09 08:15:53 |
| 138.68.50.18 | attackspam | Nov 28 23:45:55 master sshd[3968]: Failed password for root from 138.68.50.18 port 33004 ssh2 Nov 28 23:55:48 master sshd[3998]: Failed password for invalid user lakota from 138.68.50.18 port 53244 ssh2 Nov 29 00:01:39 master sshd[4746]: Failed password for invalid user bulent from 138.68.50.18 port 33478 ssh2 Nov 29 00:04:51 master sshd[4748]: Failed password for invalid user test from 138.68.50.18 port 41920 ssh2 Nov 29 00:08:03 master sshd[4750]: Failed password for root from 138.68.50.18 port 50350 ssh2 Nov 29 00:11:11 master sshd[4754]: Failed password for invalid user kumakuma from 138.68.50.18 port 58778 ssh2 Nov 29 00:14:25 master sshd[4756]: Failed password for invalid user winthrop from 138.68.50.18 port 38986 ssh2 Nov 29 00:17:34 master sshd[4770]: Failed password for root from 138.68.50.18 port 47414 ssh2 Nov 29 00:20:42 master sshd[4772]: Failed password for invalid user seamark from 138.68.50.18 port 55842 ssh2 Nov 29 00:23:43 master sshd[4774]: Failed password for invalid user rpm from 138.68.5 |
2019-11-29 06:55:19 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.50.78
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37677
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;138.68.50.78. IN A
;; AUTHORITY SECTION:
. 296 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020101001 1800 900 604800 86400
;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 11 05:34:21 CST 2020
;; MSG SIZE rcvd: 116Host 78.50.68.138.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 78.50.68.138.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 185.156.177.243 | attack | 1579869270 - 01/24/2020 19:34:30 Host: 185.156.177.243/185.156.177.243 Port: 3 TCP Blocked ... |
2020-01-25 01:26:51 |
| 85.93.52.99 | attackbots | Unauthorized connection attempt detected from IP address 85.93.52.99 to port 2220 [J] |
2020-01-25 01:21:10 |
| 113.236.25.4 | attackbotsspam | Telnet/23 MH Probe, BF, Hack - |
2020-01-25 01:50:17 |
| 42.179.210.88 | attackbotsspam | 23/tcp [2020-01-24]1pkt |
2020-01-25 01:28:09 |
| 207.148.68.148 | attackbots | 2020-01-24T17:06:49.344366shield sshd\[13253\]: Invalid user archer from 207.148.68.148 port 46772 2020-01-24T17:06:49.348626shield sshd\[13253\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.148.68.148 2020-01-24T17:06:51.115789shield sshd\[13253\]: Failed password for invalid user archer from 207.148.68.148 port 46772 ssh2 2020-01-24T17:11:47.684296shield sshd\[15715\]: Invalid user renato from 207.148.68.148 port 44334 2020-01-24T17:11:47.690119shield sshd\[15715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.148.68.148 |
2020-01-25 01:27:19 |
| 36.26.236.6 | attack | Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM - |
2020-01-25 01:39:42 |
| 190.74.65.3 | attackspam | Unauthorized connection attempt from IP address 190.74.65.3 on Port 445(SMB) |
2020-01-25 01:49:44 |
| 59.164.64.226 | attackspam | 445/tcp [2020-01-24]1pkt |
2020-01-25 01:56:50 |
| 46.12.60.53 | attackspambots | Unauthorized connection attempt detected from IP address 46.12.60.53 to port 23 [J] |
2020-01-25 01:41:25 |
| 192.210.189.176 | attackbotsspam | (From eric@talkwithcustomer.com) Hi, Let’s take a quick trip to Tomorrow-land. I’m not talking about a theme park, I’m talking about your business’s future… Don’t worry, we won’t even need a crystal ball. Just imagine… … a future where the money you invest in driving traffic to your site wellnessfirstclinics.com pays off with tons of calls from qualified leads. And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website wellnessfirstclinics.com. Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets. Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference? And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer. You installed TalkWithCustomer on wellnessfirstclinics.com – it was a snap. And practically overnig |
2020-01-25 01:47:16 |
| 91.202.197.29 | attack | 1579869260 - 01/24/2020 13:34:20 Host: 91.202.197.29/91.202.197.29 Port: 445 TCP Blocked |
2020-01-25 01:42:13 |
| 36.26.235.32 | attackbots | Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM - |
2020-01-25 01:44:19 |
| 51.89.32.193 | attack | " " |
2020-01-25 01:14:47 |
| 185.226.145.95 | attackbots | (From eric@talkwithcustomer.com) Hello portorangefamilychiropracticcenter.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website portorangefamilychiropracticcenter.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website portorangefamilychiropracticcenter.com, trying to make up their mind whether you are right for them. When you connect with them at that ve |
2020-01-25 01:53:05 |
| 178.33.175.19 | attackspam | Unauthorized connection attempt detected from IP address 178.33.175.19 to port 1433 [J] |
2020-01-25 01:23:30 |