106.13.125.241

Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: Beijing Baidu Netcom Science and Technology Co. Ltd.

Hostname: unknown

Organization: unknown

Usage Type: Search Engine Spider

Comments:

Make a comment on this IP

Type	Details	Datetime
attackbotsspam	$f2bV_matches	2020-04-04 00:46:24
attackbotsspam	$f2bV_matches	2020-03-21 13:47:03
attackspambots	Invalid user halt from 106.13.125.241 port 50382	2020-03-14 09:45:10
attackspambots	$f2bV_matches	2020-03-04 04:53:20
attackbots	Feb 12 04:46:44 ws26vmsma01 sshd[173213]: Failed password for root from 106.13.125.241 port 53569 ssh2 Feb 12 04:50:14 ws26vmsma01 sshd[183483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.241 ...	2020-02-12 19:34:46
attackspambots	Feb 4 01:50:40 markkoudstaal sshd[7205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.241 Feb 4 01:50:42 markkoudstaal sshd[7205]: Failed password for invalid user hatang from 106.13.125.241 port 42567 ssh2 Feb 4 01:53:54 markkoudstaal sshd[7844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.241	2020-02-04 08:57:31
attack	Unauthorized connection attempt detected from IP address 106.13.125.241 to port 2220 [J]	2020-01-22 01:42:37
attack	Invalid user milena from 106.13.125.241 port 46942	2020-01-19 21:54:36
attackspambots	Jan 2 07:50:25 ns3110291 sshd\[13567\]: Invalid user test from 106.13.125.241 Jan 2 07:50:25 ns3110291 sshd\[13567\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.241 Jan 2 07:50:27 ns3110291 sshd\[13567\]: Failed password for invalid user test from 106.13.125.241 port 45720 ssh2 Jan 2 07:53:03 ns3110291 sshd\[13610\]: Invalid user admin from 106.13.125.241 Jan 2 07:53:03 ns3110291 sshd\[13610\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.241 ...	2020-01-02 17:17:00

Comments on same subnet:

IP	Type	Details	Datetime
106.13.125.248	attack	(sshd) Failed SSH login from 106.13.125.248 (CN/China/-): 5 in the last 3600 secs	2020-09-25 10:21:01
106.13.125.159	attackbotsspam	Aug 28 07:50:53 ajax sshd[7922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 Aug 28 07:50:55 ajax sshd[7922]: Failed password for invalid user localhost from 106.13.125.159 port 55500 ssh2	2020-08-28 17:19:46
106.13.125.159	attackbotsspam	Automatic report - Banned IP Access	2020-08-27 23:26:13
106.13.125.159	attack	Aug 23 15:23:17 nextcloud sshd\[19344\]: Invalid user lh from 106.13.125.159 Aug 23 15:23:17 nextcloud sshd\[19344\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 Aug 23 15:23:19 nextcloud sshd\[19344\]: Failed password for invalid user lh from 106.13.125.159 port 50620 ssh2	2020-08-24 02:43:33
106.13.125.159	attackspam	Aug 14 19:43:12 xeon sshd[52456]: Failed password for root from 106.13.125.159 port 52310 ssh2	2020-08-15 02:50:00
106.13.125.159	attack	Jun 9 18:38:27 web9 sshd\[2344\]: Invalid user idempiere from 106.13.125.159 Jun 9 18:38:27 web9 sshd\[2344\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 Jun 9 18:38:29 web9 sshd\[2344\]: Failed password for invalid user idempiere from 106.13.125.159 port 52276 ssh2 Jun 9 18:41:39 web9 sshd\[2762\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 user=root Jun 9 18:41:42 web9 sshd\[2762\]: Failed password for root from 106.13.125.159 port 41158 ssh2	2020-06-10 12:44:58
106.13.125.159	attack	Apr 27 17:13:37 ns3164893 sshd[12153]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 Apr 27 17:13:39 ns3164893 sshd[12153]: Failed password for invalid user ls from 106.13.125.159 port 60408 ssh2 ...	2020-04-28 04:07:44
106.13.125.159	attack	Apr 8 07:23:19 OPSO sshd\[13431\]: Invalid user ubuntu from 106.13.125.159 port 53504 Apr 8 07:23:19 OPSO sshd\[13431\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159 Apr 8 07:23:21 OPSO sshd\[13431\]: Failed password for invalid user ubuntu from 106.13.125.159 port 53504 ssh2 Apr 8 07:28:16 OPSO sshd\[14845\]: Invalid user fiscal from 106.13.125.159 port 46406 Apr 8 07:28:16 OPSO sshd\[14845\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.159	2020-04-08 18:17:29
106.13.125.84	attack	Mar 25 10:29:09 server sshd\[8981\]: Invalid user yangjie from 106.13.125.84 Mar 25 10:29:09 server sshd\[8981\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 Mar 25 10:29:11 server sshd\[8981\]: Failed password for invalid user yangjie from 106.13.125.84 port 40336 ssh2 Mar 25 10:48:01 server sshd\[14266\]: Invalid user vg from 106.13.125.84 Mar 25 10:48:01 server sshd\[14266\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 ...	2020-03-25 15:56:05
106.13.125.159	attackbotsspam	Invalid user sanjay from 106.13.125.159 port 54336	2020-03-21 16:47:27
106.13.125.84	attackspambots	$f2bV_matches	2020-03-19 07:30:22
106.13.125.84	attackspam	(sshd) Failed SSH login from 106.13.125.84 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 13 23:07:34 srv sshd[11082]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 user=root Mar 13 23:07:37 srv sshd[11082]: Failed password for root from 106.13.125.84 port 56668 ssh2 Mar 13 23:12:09 srv sshd[11208]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 user=root Mar 13 23:12:11 srv sshd[11208]: Failed password for root from 106.13.125.84 port 50064 ssh2 Mar 13 23:16:19 srv sshd[11262]: Invalid user account from 106.13.125.84 port 47842	2020-03-14 06:08:44
106.13.125.159	attackbots	Too many connections or unauthorized access detected from Arctic banned ip	2020-03-12 14:10:38
106.13.125.84	attackspambots	Mar 9 00:32:09 lukav-desktop sshd\[24421\]: Invalid user yang from 106.13.125.84 Mar 9 00:32:09 lukav-desktop sshd\[24421\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 Mar 9 00:32:11 lukav-desktop sshd\[24421\]: Failed password for invalid user yang from 106.13.125.84 port 40398 ssh2 Mar 9 00:34:19 lukav-desktop sshd\[24437\]: Invalid user ftpuser from 106.13.125.84 Mar 9 00:34:19 lukav-desktop sshd\[24437\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84	2020-03-09 07:18:24
106.13.125.84	attack	Mar 5 15:30:57 lukav-desktop sshd\[11350\]: Invalid user tss from 106.13.125.84 Mar 5 15:30:57 lukav-desktop sshd\[11350\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84 Mar 5 15:30:59 lukav-desktop sshd\[11350\]: Failed password for invalid user tss from 106.13.125.84 port 55292 ssh2 Mar 5 15:34:50 lukav-desktop sshd\[11425\]: Invalid user deployer from 106.13.125.84 Mar 5 15:34:50 lukav-desktop sshd\[11425\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.125.84	2020-03-05 23:15:05

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.13.125.241
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52334
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;106.13.125.241.			IN	A

;; AUTHORITY SECTION:
.			516	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2020010200 1800 900 604800 86400

;; Query time: 892 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 02 17:16:57 CST 2020
;; MSG SIZE  rcvd: 118

Host info

Host 241.125.13.106.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 241.125.13.106.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
139.180.154.148	attackspam	Lines containing failures of 139.180.154.148 Sep 30 22:09:46 rancher sshd[12525]: Invalid user kube from 139.180.154.148 port 37468 Sep 30 22:09:46 rancher sshd[12525]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.154.148 Sep 30 22:09:48 rancher sshd[12525]: Failed password for invalid user kube from 139.180.154.148 port 37468 ssh2 Sep 30 22:09:49 rancher sshd[12525]: Received disconnect from 139.180.154.148 port 37468:11: Bye Bye [preauth] Sep 30 22:09:49 rancher sshd[12525]: Disconnected from invalid user kube 139.180.154.148 port 37468 [preauth] Sep 30 22:19:55 rancher sshd[12760]: Invalid user production from 139.180.154.148 port 46210 Sep 30 22:19:55 rancher sshd[12760]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.154.148 Sep 30 22:19:57 rancher sshd[12760]: Failed password for invalid user production from 139.180.154.148 port 46210 ssh2 Sep 30 22:19:58 rancher ssh........ ------------------------------	2020-10-01 12:20:10
5.193.136.180	attackspambots	57458/udp [2020-09-30]1pkt	2020-10-01 12:04:19
106.13.161.17	attackspam	s3.hscode.pl - SSH Attack	2020-10-01 09:14:47
139.59.78.248	attackbots	CMS (WordPress or Joomla) login attempt.	2020-10-01 12:23:49
216.98.211.118	attackbotsspam	445/tcp [2020-09-30]1pkt	2020-10-01 12:31:25
35.195.238.142	attackspambots	Oct 1 03:30:55 serwer sshd\[19213\]: Invalid user shoutcast from 35.195.238.142 port 43660 Oct 1 03:30:55 serwer sshd\[19213\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.195.238.142 Oct 1 03:30:57 serwer sshd\[19213\]: Failed password for invalid user shoutcast from 35.195.238.142 port 43660 ssh2 ...	2020-10-01 12:30:46
34.72.78.90	attackbots	20 attempts against mh-ssh on cloud	2020-10-01 12:09:47
202.153.230.26	attack	445/tcp [2020-09-30]1pkt	2020-10-01 12:32:45
54.79.183.95	spamattack	54.79.183.95 - - [01/Oct/2020:11:23:32 +1000] "GET /NlpsnoP83Wm7 HTTP/1.1" 404 28236 "-" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36" 54.79.183.95 - - [01/Oct/2020:11:23:34 +1000] "GET /kwhEYwj0hOyL.php HTTP/1.1" 404 28182 "-" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36" 54.79.183.95 - - [01/Oct/2020:11:23:33 +1000] "GET /KlaebCadFcK1/ HTTP/1.1" 404 28181 "-" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36" 54.79.183.95 - - [01/Oct/2020:11:23:32 +1000] "GET /NlpsnoP83Wm7 HTTP/1.1" 404 28236 "-" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36"	2020-10-01 11:46:34
177.154.226.89	attackspam	(smtpauth) Failed SMTP AUTH login from 177.154.226.89 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-10-01 00:11:51 plain authenticator failed for ([177.154.226.89]) [177.154.226.89]: 535 Incorrect authentication data (set_id=info)	2020-10-01 12:10:48
212.18.22.236	attackspambots	$f2bV_matches	2020-10-01 12:33:29
87.251.70.83	attackspam	port scan and connect, tcp 8080 (http-proxy)	2020-10-01 12:17:34
78.46.45.141	attackspam	Fail2Ban Ban Triggered Wordpress Attack Attempt	2020-10-01 12:37:16
197.60.176.182	attackspam	23/tcp [2020-09-30]1pkt	2020-10-01 12:28:01
27.110.164.162	attack	TCP (SYN) 27.110.164.162:18109 -> port 23, len 44	2020-10-01 12:10:01

Recently Reported IPs

187.162.48.9	63.81.87.72	14.233.242.218	14.170.145.36
95.178.159.193	216.10.217.18	136.101.250.162	14.165.183.252
116.175.212.143	49.73.229.214	209.212.242.69	50.60.18.164
113.169.83.75	81.112.254.116	95.178.157.213	168.205.38.137
46.237.7.67	49.34.42.9	183.89.45.192	117.211.43.137