This IP address has been reported a total of
490
times from
285 distinct
sources.
134.122.60.26 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-02-09T02:16:41.581785+00:00 news2.dwmp.it sshd[1678440]: Failed password for root from 134.122. ...
show more2026-02-09T02:16:41.581785+00:00 news2.dwmp.it sshd[1678440]: Failed password for root from 134.122.60.26 port 45700 ssh2
2026-02-09T02:17:58.661333+00:00 news2.dwmp.it sshd[1678693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.60.26 user=root
2026-02-09T02:18:01.172457+00:00 news2.dwmp.it sshd[1678693]: Failed password for root from 134.122.60.26 port 36640 ssh2
...
show less
Feb 9 04:16:03 cloud10504 sshd[185585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ...
show moreFeb 9 04:16:03 cloud10504 sshd[185585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.60.26 user=root
Feb 9 04:16:04 cloud10504 sshd[185585]: Failed password for invalid user root from 134.122.60.26 port 57898 ssh2
Feb 9 04:17:21 cloud10504 sshd[185650]: User root from 134.122.60.26 not allowed because not listed in AllowUsers
...
show less
Brute-Force
SSH
Anonymous
2026-02-09T03:14:31.311814v22019037947384217 sshd[19331]: Did not receive identification string from ...
show more2026-02-09T03:14:31.311814v22019037947384217 sshd[19331]: Did not receive identification string from 134.122.60.26 port 60178
2026-02-09T03:15:45.277207v22019037947384217 sshd[19335]: Connection closed by 134.122.60.26 port 48878 [preauth]
2026-02-09T03:17:06.378419v22019037947384217 sshd[19352]: Connection closed by 134.122.60.26 port 37232 [preauth]
...
show less
Brute-Force
SSH
Anonymous
(sshd) Failed SSH login from 134.122.60.26 (NL/The Netherlands/-): 4 in the last 3600 secs; Ports: * ...
show more(sshd) Failed SSH login from 134.122.60.26 (NL/The Netherlands/-): 4 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 9 02:14:29 xn--80aqlfee4d sshd[26277]: Did not receive identification string from 134.122.60.26
Feb 9 02:15:43 xn--80aqlfee4d sshd[26522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.60.26 user=root
Feb 9 02:15:45 xn--80aqlfee4d sshd[26522]: Failed password for root from 134.122.60.26 port 53038 ssh2
Feb 9 02:16:59 xn--80aqlfee4d sshd[26744]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.60.26 user=root
show less
2026-02-09T03:15:18.208213+01:00 aligw01.aneirin.net sshd-session[39149]: Failed password for root f ...
show more2026-02-09T03:15:18.208213+01:00 aligw01.aneirin.net sshd-session[39149]: Failed password for root from 134.122.60.26 port 56172 ssh2
2026-02-09T03:15:20.169620+01:00 aligw01.aneirin.net sshd-session[39149]: Connection closed by authenticating user root 134.122.60.26 port 56172 [preauth]
2026-02-09T03:16:38.906761+01:00 aligw01.aneirin.net sshd-session[39156]: Failed password for root from 134.122.60.26 port 52032 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 490 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩