This IP address has been reported a total of
130
times from
113 distinct
sources.
139.59.36.73 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
2026-03-11T22:11:40.659913+00:00 us-lax-node1121 sshd-session[1084880]: Failed password for root fro ...
show more2026-03-11T22:11:40.659913+00:00 us-lax-node1121 sshd-session[1084880]: Failed password for root from 139.59.36.73 port 60374 ssh2
2026-03-11T22:12:39.938571+00:00 us-lax-node1121 sshd-session[1085009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
2026-03-11T22:12:42.374352+00:00 us-lax-node1121 sshd-session[1085009]: Failed password for root from 139.59.36.73 port 51700 ssh2
...
show less
Connection closed by authenticating user root 139.59.36.73 port 45006 [preauth]
Connection closed by ...
show moreConnection closed by authenticating user root 139.59.36.73 port 45006 [preauth]
Connection closed by authenticating user root 139.59.36.73 port 42564 [preauth]
Connection closed by authenticating user root 139.59.36.73 port 43424 [preauth]
Connection closed by authenticating user root 139.59.36.73 port 38144 [preauth]
Connection closed by authenticating user root 139.59.36.73 port 44692 [preauth]
show less
2026-03-11T22:12:12.511719+00:00 rpi5 sshd[321833]: Failed password for root from 139.59.36.73 port ...
show more2026-03-11T22:12:12.511719+00:00 rpi5 sshd[321833]: Failed password for root from 139.59.36.73 port 35228 ssh2
2026-03-11T22:13:10.853943+00:00 rpi5 sshd[321879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
2026-03-11T22:13:12.962605+00:00 rpi5 sshd[321879]: Failed password for root from 139.59.36.73 port 44920 ssh2
...
show less
2026-03-12T01:12:10.035435tim.mtkrbti.by sshd[1148]: Failed password for root from 139.59.36.73 port ...
show more2026-03-12T01:12:10.035435tim.mtkrbti.by sshd[1148]: Failed password for root from 139.59.36.73 port 48004 ssh2
2026-03-12T01:13:07.729166tim.mtkrbti.by sshd[1154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
2026-03-12T01:13:09.758022tim.mtkrbti.by sshd[1154]: Failed password for root from 139.59.36.73 port 54156 ssh2
...
show less
2026-03-11T22:11:40.659913+00:00 us-lax-node1121 sshd-session[1084880]: Failed password for root fro ...
show more2026-03-11T22:11:40.659913+00:00 us-lax-node1121 sshd-session[1084880]: Failed password for root from 139.59.36.73 port 60374 ssh2
2026-03-11T22:12:39.938571+00:00 us-lax-node1121 sshd-session[1085009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
2026-03-11T22:12:42.374352+00:00 us-lax-node1121 sshd-session[1085009]: Failed password for root from 139.59.36.73 port 51700 ssh2
...
show less
Mar 12 00:11:07 server5 sshd[290381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eu ...
show moreMar 12 00:11:07 server5 sshd[290381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
Mar 12 00:11:09 server5 sshd[290381]: Failed password for invalid user root from 139.59.36.73 port 33886 ssh2
Mar 12 00:12:10 server5 sshd[290386]: User root from 139.59.36.73 not allowed because not listed in AllowUsers
...
show less
Mar 11 15:10:44 servidor sshd[685802]: Connection closed by authenticating user root 139.59.36.73 po ...
show moreMar 11 15:10:44 servidor sshd[685802]: Connection closed by authenticating user root 139.59.36.73 port 59558 [preauth]
Mar 11 15:11:46 servidor sshd[685849]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.36.73 user=root
Mar 11 15:11:48 servidor sshd[685849]: Failed password for root from 139.59.36.73 port 51160 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 130 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩