This IP address has been reported a total of
406
times from
142 distinct
sources.
139.59.46.142 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-03T18:36:40.048461+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38734]: Invalid user ubuntu from 13 ...
show more2026-03-03T18:36:40.048461+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38734]: Invalid user ubuntu from 139.59.46.142 port 35820
2026-03-03T18:36:40.196166+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38734]: Connection closed by invalid user ubuntu 139.59.46.142 port 35820 [preauth]
...
show less
2026-03-03T18:21:06.376757+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38637]: Invalid user admin from 139 ...
show more2026-03-03T18:21:06.376757+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38637]: Invalid user admin from 139.59.46.142 port 39554
2026-03-03T18:21:06.524286+00:00 ubuntu-s-1vcpu-1gb-lon1-01 sshd[38637]: Connection closed by invalid user admin 139.59.46.142 port 39554 [preauth]
...
show less
Mar 3 18:17:00 localhost sshd[17375]: Invalid user admin from 139.59.46.142 port 39650
Mar 3 18:17 ...
show moreMar 3 18:17:00 localhost sshd[17375]: Invalid user admin from 139.59.46.142 port 39650
Mar 3 18:17:36 localhost sshd[17384]: Invalid user admin from 139.59.46.142 port 41010
Mar 3 18:18:14 localhost sshd[17389]: Invalid user admin from 139.59.46.142 port 55570
Mar 3 18:18:51 localhost sshd[17396]: Invalid user admin from 139.59.46.142 port 50316
Mar 3 18:19:28 localhost sshd[17400]: Invalid user admin from 139.59.46.142 port 39750
...
show less
2026-03-03T18:17:00.561303+00:00 worker-lon1 sshd[718287]: Invalid user admin from 139.59.46.142 por ...
show more2026-03-03T18:17:00.561303+00:00 worker-lon1 sshd[718287]: Invalid user admin from 139.59.46.142 port 49222
2026-03-03T18:17:36.994337+00:00 worker-lon1 sshd[718301]: Invalid user admin from 139.59.46.142 port 35556
2026-03-03T18:18:15.207543+00:00 worker-lon1 sshd[718317]: Invalid user admin from 139.59.46.142 port 45440
2026-03-03T18:18:51.951821+00:00 worker-lon1 sshd[718329]: Invalid user admin from 139.59.46.142 port 50548
2026-03-03T18:19:29.211414+00:00 worker-lon1 sshd[718340]: Invalid user admin from 139.59.46.142 port 56164
...
show less
2026-03-03T18:17:21.258506+00:00 vps-ed343ff6 sshd[3645915]: Invalid user admin from 139.59.46.142 p ...
show more2026-03-03T18:17:21.258506+00:00 vps-ed343ff6 sshd[3645915]: Invalid user admin from 139.59.46.142 port 44316
2026-03-03T18:17:58.106933+00:00 vps-ed343ff6 sshd[3646289]: Invalid user admin from 139.59.46.142 port 59726
2026-03-03T18:18:36.199961+00:00 vps-ed343ff6 sshd[3646549]: Invalid user admin from 139.59.46.142 port 54170
...
show less
2026-03-03T19:17:15.770363+01:00 gw4 sshd-session[4141603]: Invalid user admin from 139.59.46.142 po ...
show more2026-03-03T19:17:15.770363+01:00 gw4 sshd-session[4141603]: Invalid user admin from 139.59.46.142 port 36156
2026-03-03T19:17:52.748191+01:00 gw4 sshd-session[4141718]: Invalid user admin from 139.59.46.142 port 47064
2026-03-03T19:18:30.441460+01:00 gw4 sshd-session[4141867]: Invalid user admin from 139.59.46.142 port 48228
...
show less
2026-03-03T18:17:16.802253+00:00 ns536341 sshd-session[41467]: Invalid user admin from 139.59.46.142 ...
show more2026-03-03T18:17:16.802253+00:00 ns536341 sshd-session[41467]: Invalid user admin from 139.59.46.142 port 58510
2026-03-03T18:17:53.642218+00:00 ns536341 sshd-session[41471]: Invalid user admin from 139.59.46.142 port 33456
2026-03-03T18:18:31.270128+00:00 ns536341 sshd-session[41475]: Invalid user admin from 139.59.46.142 port 48508
...
show less
2026-03-03T18:17:58.751632+00:00 vm22 sshd-session[874251]: Connection from 139.59.46.142 port 54140 ...
show more2026-03-03T18:17:58.751632+00:00 vm22 sshd-session[874251]: Connection from 139.59.46.142 port 54140 on 139.59.189.208 port 22 rdomain ""
2026-03-03T18:17:59.507054+00:00 vm22 sshd-session[874251]: Invalid user admin from 139.59.46.142 port 54140
...
show less
Brute-Force
SSH
Anonymous
2026-03-03 20:05:28,987 fail2ban.actions [3109230]: NOTICE [sshd] Ban 139.59.46.142
2026-03- ...
show more2026-03-03 20:05:28,987 fail2ban.actions [3109230]: NOTICE [sshd] Ban 139.59.46.142
2026-03-03 20:16:32,266 fail2ban.actions [3109230]: NOTICE [sshd] Ban 139.59.46.142
...
show less
Brute-Force
Exploited Host
Anonymous
2026-03-03T18:06:35.341101+00:00 web01.mdo-cloud.net sshd[231440]: Failed password for root from 139 ...
show more2026-03-03T18:06:35.341101+00:00 web01.mdo-cloud.net sshd[231440]: Failed password for root from 139.59.46.142 port 36710 ssh2
2026-03-03T18:07:12.698942+00:00 web01.mdo-cloud.net sshd[231449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.46.142 user=root
2026-03-03T18:07:14.402311+00:00 web01.mdo-cloud.net sshd[231449]: Failed password for root from 139.59.46.142 port 46792 ssh2
2026-03-03T18:07:50.463330+00:00 web01.mdo-cloud.net sshd[231458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.46.142 user=root
2026-03-03T18:07:52.382264+00:00 web01.mdo-cloud.net sshd[231458]: Failed password for root from 139.59.46.142 port 47048 ssh2
...
show less
Brute-Force
SSH
Web App Attack
FTP Brute-Force
Port Scan
Hacking
Showing 1 to
15
of 406 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩