This IP address has been reported a total of
221
times from
109 distinct
sources.
59.144.173.119 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
2026-06-30T01:21:46.391190+02:00 **** sshd-session[4929]: Invalid user **** from 59.144.173.119 port ...
show more2026-06-30T01:21:46.391190+02:00 **** sshd-session[4929]: Invalid user **** from 59.144.173.119 port 46884
2026-06-30T01:21:46.591504+02:00 **** sshd-session[4929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.144.173.119
2026-06-30T01:21:48.833914+02:00 **** sshd-session[4929]: Failed password for invalid user **** from 59.144.173.119 port 46884 ssh2
2026-06-30T01:22:05.569179+02:00 **** sshd-session[5258]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.144.173.119 user=root
2026-06-30T01:22:07.749546+02:00 **** sshd-session[5258]: Failed password for root from 59.144.173.119 port 41272 ssh2
show less
2026-06-29T12:51:20.153442+02:00 srv03 sshd[4046918]: Invalid user user from 59.144.173.119 port 546 ...
show more2026-06-29T12:51:20.153442+02:00 srv03 sshd[4046918]: Invalid user user from 59.144.173.119 port 54638
2026-06-29T12:54:21.912296+02:00 srv03 sshd[4047502]: Invalid user avis from 59.144.173.119 port 50002
2026-06-29T12:55:47.843120+02:00 srv03 sshd[4047871]: Invalid user zimbra from 59.144.173.119 port 41488
2026-06-29T12:56:05.160657+02:00 srv03 sshd[4048031]: Invalid user admin from 59.144.173.119 port 33630
2026-06-29T12:56:21.803048+02:00 srv03 sshd[4048054]: Invalid user user from 59.144.173.119 port 44572
...
show less
2026-06-23T12:16:30.301781+01:00 kakarott sshd[3347570]: Invalid user sugon from 59.144.173.119 port ...
show more2026-06-23T12:16:30.301781+01:00 kakarott sshd[3347570]: Invalid user sugon from 59.144.173.119 port 35848
2026-06-23T12:16:47.288445+01:00 kakarott sshd[3347572]: Invalid user server from 59.144.173.119 port 41990
show less
2026-06-23T09:26:09.877338+02:00 server2 sshd[3596656]: Invalid user hzzt from 59.144.173.119 port 3 ...
show more2026-06-23T09:26:09.877338+02:00 server2 sshd[3596656]: Invalid user hzzt from 59.144.173.119 port 38734
2026-06-23T09:28:37.062746+02:00 server2 sshd[3596898]: Invalid user user from 59.144.173.119 port 38702
2026-06-23T09:28:54.393285+02:00 server2 sshd[3596926]: Invalid user es from 59.144.173.119 port 54190
...
show less
Port Scan
Hacking
Brute-Force
Bad Web Bot
SSH
Web App Attack
F2B sshd ban. Logs: 2026-06-22T03:07:27.076980+02:00 isp sshd[857783]: Connection closed by 59.144.1 ...
show moreF2B sshd ban. Logs: 2026-06-22T03:07:27.076980+02:00 isp sshd[857783]: Connection closed by 59.144.173.119 port 37266 [preauth]
show less
2026-06-21T20:32:18.764734+02:00 rserver.lirion.de sshd-session[3145080]: Invalid user localhost fro ...
show more2026-06-21T20:32:18.764734+02:00 rserver.lirion.de sshd-session[3145080]: Invalid user localhost from 59.144.173.119 port 58422
2026-06-21T20:32:56.240740+02:00 rserver.lirion.de sshd-session[3145163]: Invalid user docker from 59.144.173.119 port 44608
2026-06-21T20:33:15.170252+02:00 rserver.lirion.de sshd-session[3145209]: Invalid user dani from 59.144.173.119 port 44330
2026-06-21T20:33:50.601162+02:00 rserver.lirion.de sshd-session[3145295]: Invalid user jatten from 59.144.173.119 port 41898
...
show less
2026-06-18T04:45:08.941404 vmi2089077.contaboserver.net sshd[2909369]: Invalid user baobao from 59.1 ...
show more2026-06-18T04:45:08.941404 vmi2089077.contaboserver.net sshd[2909369]: Invalid user baobao from 59.144.173.119 port 42452
2026-06-18T04:45:29.500148 vmi2089077.contaboserver.net sshd[2909498]: Invalid user lishiqi from 59.144.173.119 port 49370
2026-06-18T04:45:51.229510 vmi2089077.contaboserver.net sshd[2909653]: Invalid user jxz from 59.144.173.119 port 41854
...
show less
Brute-Force
SSH
Showing 1 to
15
of 221 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩