Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Spain

Internet Service Provider: OVH SAS

Hostname: unknown

Organization: OVH SAS

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
Dec  3 06:44:02 firewall sshd[12627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Dec  3 06:44:02 firewall sshd[12627]: Invalid user rimey from 164.132.80.137
Dec  3 06:44:04 firewall sshd[12627]: Failed password for invalid user rimey from 164.132.80.137 port 36346 ssh2
...
2019-12-03 21:57:54
attack
2019-12-01T07:27:28.395976vps751288.ovh.net sshd\[19049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137  user=root
2019-12-01T07:27:29.912009vps751288.ovh.net sshd\[19049\]: Failed password for root from 164.132.80.137 port 36804 ssh2
2019-12-01T07:30:09.069957vps751288.ovh.net sshd\[19057\]: Invalid user ethereal from 164.132.80.137 port 43384
2019-12-01T07:30:09.077325vps751288.ovh.net sshd\[19057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
2019-12-01T07:30:11.029688vps751288.ovh.net sshd\[19057\]: Failed password for invalid user ethereal from 164.132.80.137 port 43384 ssh2
2019-12-01 15:18:17
attack
Nov 25 12:54:50 TORMINT sshd\[31221\]: Invalid user Passw0rd1 from 164.132.80.137
Nov 25 12:54:50 TORMINT sshd\[31221\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Nov 25 12:54:52 TORMINT sshd\[31221\]: Failed password for invalid user Passw0rd1 from 164.132.80.137 port 49534 ssh2
...
2019-11-26 02:10:43
attack
Nov 24 12:47:59 vibhu-HP-Z238-Microtower-Workstation sshd\[13585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137  user=news
Nov 24 12:48:01 vibhu-HP-Z238-Microtower-Workstation sshd\[13585\]: Failed password for news from 164.132.80.137 port 52522 ssh2
Nov 24 12:54:19 vibhu-HP-Z238-Microtower-Workstation sshd\[13782\]: Invalid user francis from 164.132.80.137
Nov 24 12:54:19 vibhu-HP-Z238-Microtower-Workstation sshd\[13782\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Nov 24 12:54:21 vibhu-HP-Z238-Microtower-Workstation sshd\[13782\]: Failed password for invalid user francis from 164.132.80.137 port 60544 ssh2
...
2019-11-24 15:40:19
attackspambots
May 10 19:38:23 server sshd\[68647\]: Invalid user fv from 164.132.80.137
May 10 19:38:23 server sshd\[68647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
May 10 19:38:25 server sshd\[68647\]: Failed password for invalid user fv from 164.132.80.137 port 54106 ssh2
...
2019-10-09 15:23:14
attackbotsspam
2019-07-28T16:10:55.424337abusebot-2.cloudsearch.cf sshd\[28677\]: Invalid user william123 from 164.132.80.137 port 44970
2019-07-29 04:23:02
attack
Jul 25 14:37:32 pornomens sshd\[1145\]: Invalid user joerg from 164.132.80.137 port 57164
Jul 25 14:37:32 pornomens sshd\[1145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Jul 25 14:37:34 pornomens sshd\[1145\]: Failed password for invalid user joerg from 164.132.80.137 port 57164 ssh2
...
2019-07-25 23:52:02
attack
Mar 20 18:27:53 vpn sshd[31897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Mar 20 18:27:55 vpn sshd[31897]: Failed password for invalid user brian from 164.132.80.137 port 60224 ssh2
Mar 20 18:36:00 vpn sshd[31903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
2019-07-19 11:42:21
attackspam
Jun 24 19:59:51 TORMINT sshd\[3129\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137  user=root
Jun 24 19:59:53 TORMINT sshd\[3129\]: Failed password for root from 164.132.80.137 port 48150 ssh2
Jun 24 20:01:20 TORMINT sshd\[3242\]: Invalid user balance from 164.132.80.137
Jun 24 20:01:20 TORMINT sshd\[3242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
...
2019-06-25 13:37:57
Comments on same subnet:
IP Type Details Datetime
164.132.80.139 attack
$f2bV_matches
2020-02-22 09:02:47
164.132.80.139 attackspambots
$f2bV_matches
2020-02-17 13:02:30
164.132.80.139 attack
Feb  9 05:04:12 marvibiene sshd[55276]: Invalid user rng from 164.132.80.139 port 33488
Feb  9 05:04:12 marvibiene sshd[55276]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Feb  9 05:04:12 marvibiene sshd[55276]: Invalid user rng from 164.132.80.139 port 33488
Feb  9 05:04:14 marvibiene sshd[55276]: Failed password for invalid user rng from 164.132.80.139 port 33488 ssh2
...
2020-02-09 19:35:54
164.132.80.139 attack
Unauthorized connection attempt detected from IP address 164.132.80.139 to port 2220 [J]
2020-02-06 08:30:57
164.132.80.139 attackspam
SSH Brute Force
2020-02-04 08:11:34
164.132.80.139 attackbotsspam
Jan 18 18:27:38 dedicated sshd[6877]: Invalid user webmaster from 164.132.80.139 port 34350
2020-01-19 01:40:37
164.132.80.139 attackspambots
Jan 17 19:16:33 ns382633 sshd\[27008\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139  user=root
Jan 17 19:16:36 ns382633 sshd\[27008\]: Failed password for root from 164.132.80.139 port 38592 ssh2
Jan 17 19:25:10 ns382633 sshd\[28633\]: Invalid user sftp from 164.132.80.139 port 35608
Jan 17 19:25:10 ns382633 sshd\[28633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Jan 17 19:25:12 ns382633 sshd\[28633\]: Failed password for invalid user sftp from 164.132.80.139 port 35608 ssh2
2020-01-18 04:27:21
164.132.80.139 attackbots
Unauthorized connection attempt detected from IP address 164.132.80.139 to port 2220 [J]
2020-01-17 03:14:44
164.132.80.139 attackspam
Jan 13 23:48:16 vps691689 sshd[29100]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Jan 13 23:48:18 vps691689 sshd[29100]: Failed password for invalid user hosting from 164.132.80.139 port 46700 ssh2
...
2020-01-14 06:53:23
164.132.80.139 attackspam
Unauthorized connection attempt detected from IP address 164.132.80.139 to port 2220 [J]
2020-01-08 04:44:03
164.132.80.139 attack
Aug 18 20:11:25 server sshd\[148991\]: Invalid user sss from 164.132.80.139
Aug 18 20:11:25 server sshd\[148991\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Aug 18 20:11:27 server sshd\[148991\]: Failed password for invalid user sss from 164.132.80.139 port 32862 ssh2
...
2019-10-09 15:22:22
164.132.80.139 attackbotsspam
Automated report - ssh fail2ban:
Sep 3 08:23:35 authentication failure 
Sep 3 08:23:36 wrong password, user=betyortodontia, port=47500, ssh2
Sep 3 08:27:29 authentication failure
2019-09-03 14:46:57
164.132.80.139 attack
Sep  1 19:42:23 MK-Soft-VM5 sshd\[27287\]: Invalid user ht from 164.132.80.139 port 44810
Sep  1 19:42:23 MK-Soft-VM5 sshd\[27287\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Sep  1 19:42:25 MK-Soft-VM5 sshd\[27287\]: Failed password for invalid user ht from 164.132.80.139 port 44810 ssh2
...
2019-09-02 04:23:30
164.132.80.139 attackbotsspam
Aug 29 22:03:33 kapalua sshd\[27333\]: Invalid user filter from 164.132.80.139
Aug 29 22:03:33 kapalua sshd\[27333\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Aug 29 22:03:35 kapalua sshd\[27333\]: Failed password for invalid user filter from 164.132.80.139 port 35492 ssh2
Aug 29 22:07:21 kapalua sshd\[27687\]: Invalid user bz from 164.132.80.139
Aug 29 22:07:21 kapalua sshd\[27687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
2019-08-30 17:30:03
164.132.80.139 attackbotsspam
Aug 28 09:49:43 dallas01 sshd[20591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.139
Aug 28 09:49:45 dallas01 sshd[20591]: Failed password for invalid user nan from 164.132.80.139 port 37716 ssh2
Aug 28 09:53:35 dallas01 sshd[21368]: Failed password for root from 164.132.80.139 port 53682 ssh2
2019-08-28 22:53:55
Whois info:
b
Dig info:

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Sat Apr 13 10:21:29 +08 2019
;; MSG SIZE  rcvd: 118

Host info
137.80.132.164.in-addr.arpa has no PTR record
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
*** Can't find 137.80.132.164.in-addr.arpa.: No answer

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
221.231.49.220 attackspam
20 attempts against mh-ssh on beach
2020-08-11 03:10:55
183.51.120.115 attack
Icarus honeypot on github
2020-08-11 02:51:40
189.213.37.26 attackbots
Automatic report - Port Scan Attack
2020-08-11 02:48:12
188.213.49.223 attack
Unauthorized connection attempt from IP address 188.213.49.223 on Port 445(SMB)
2020-08-11 03:12:46
78.188.150.143 attack
Port Scan
...
2020-08-11 03:09:09
180.76.177.237 attack
bruteforce detected
2020-08-11 02:46:17
171.239.189.155 attackbotsspam
Unauthorized connection attempt from IP address 171.239.189.155 on Port 445(SMB)
2020-08-11 02:56:10
104.248.176.46 attack
" "
2020-08-11 03:01:06
201.87.255.51 attack
1597060938 - 08/10/2020 14:02:18 Host: 201.87.255.51/201.87.255.51 Port: 445 TCP Blocked
2020-08-11 02:47:03
193.56.28.102 attack
Aug 10 19:50:27 blackbee postfix/smtpd[17088]: warning: unknown[193.56.28.102]: SASL LOGIN authentication failed: authentication failure
Aug 10 19:52:14 blackbee postfix/smtpd[17092]: warning: unknown[193.56.28.102]: SASL LOGIN authentication failed: authentication failure
Aug 10 19:54:04 blackbee postfix/smtpd[17103]: warning: unknown[193.56.28.102]: SASL LOGIN authentication failed: authentication failure
Aug 10 19:55:58 blackbee postfix/smtpd[17120]: warning: unknown[193.56.28.102]: SASL LOGIN authentication failed: authentication failure
Aug 10 19:57:51 blackbee postfix/smtpd[17120]: warning: unknown[193.56.28.102]: SASL LOGIN authentication failed: authentication failure
...
2020-08-11 02:58:45
109.62.140.166 attackspam
Unauthorized connection attempt from IP address 109.62.140.166 on Port 445(SMB)
2020-08-11 02:34:28
125.89.152.87 attackbotsspam
Bruteforce detected by fail2ban
2020-08-11 02:48:41
191.234.163.104 attack
Aug 10 19:54:59 rotator sshd\[1792\]: Failed password for root from 191.234.163.104 port 46136 ssh2Aug 10 19:57:52 rotator sshd\[2583\]: Failed password for root from 191.234.163.104 port 50902 ssh2Aug 10 19:58:55 rotator sshd\[2600\]: Failed password for root from 191.234.163.104 port 36190 ssh2Aug 10 19:59:58 rotator sshd\[2609\]: Failed password for root from 191.234.163.104 port 49696 ssh2Aug 10 20:01:09 rotator sshd\[3402\]: Failed password for root from 191.234.163.104 port 35004 ssh2Aug 10 20:02:16 rotator sshd\[3418\]: Failed password for root from 191.234.163.104 port 48530 ssh2
...
2020-08-11 03:06:16
103.59.59.74 attackbots
Attempted Brute Force (dovecot)
2020-08-11 03:04:10
51.137.89.155 attack
2020-08-10T18:58:04.183671hostname sshd[14338]: Failed password for root from 51.137.89.155 port 51302 ssh2
2020-08-10T19:02:25.318056hostname sshd[16083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.137.89.155  user=root
2020-08-10T19:02:26.922592hostname sshd[16083]: Failed password for root from 51.137.89.155 port 58932 ssh2
...
2020-08-11 02:40:05

Recently Reported IPs

81.22.45.219 107.170.237.161 128.199.196.155 89.251.47.186
200.77.186.195 203.205.34.228 139.0.9.163 94.249.62.59
89.38.150.236 51.68.171.195 177.1.241.154 101.236.29.126
77.42.101.115 200.72.209.66 187.189.109.138 180.252.17.21
202.28.16.8 61.184.247.4 190.64.68.178 147.202.26.150