This IP address has been reported a total of
65
times from
50 distinct
sources.
134.122.56.104 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-11T16:16:06.606154+00:00 vps-b43e0d3e sshd-session[3948460]: pam_unix(sshd:auth): authentica ...
show more2026-02-11T16:16:06.606154+00:00 vps-b43e0d3e sshd-session[3948460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
2026-02-11T16:16:08.500351+00:00 vps-b43e0d3e sshd-session[3948460]: Failed password for invalid user test from 134.122.56.104 port 47524 ssh2
2026-02-11T16:16:40.033230+00:00 vps-b43e0d3e sshd-session[3948488]: Invalid user test from 134.122.56.104 port 59618
2026-02-11T16:16:40.269510+00:00 vps-b43e0d3e sshd-session[3948488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
2026-02-11T16:16:42.017847+00:00 vps-b43e0d3e sshd-session[3948488]: Failed password for invalid user test from 134.122.56.104 port 59618 ssh2
...
show less
2026-02-11T17:15:53.328945+01:00 weberin sshd[768878]: pam_unix(sshd:auth): authentication failure; ...
show more2026-02-11T17:15:53.328945+01:00 weberin sshd[768878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
2026-02-11T17:15:55.484879+01:00 weberin sshd[768878]: Failed password for invalid user test from 134.122.56.104 port 35208 ssh2
2026-02-11T17:16:27.274857+01:00 weberin sshd[768894]: Invalid user test from 134.122.56.104 port 46860
2026-02-11T17:16:27.286699+01:00 weberin sshd[768894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
2026-02-11T17:16:28.775575+01:00 weberin sshd[768894]: Failed password for invalid user test from 134.122.56.104 port 46860 ssh2
...
show less
2026-02-11T17:15:51.925256+01:00 nospam3 sshd[540495]: Invalid user test from 134.122.56.104 port 52 ...
show more2026-02-11T17:15:51.925256+01:00 nospam3 sshd[540495]: Invalid user test from 134.122.56.104 port 52806
2026-02-11T17:16:25.588268+01:00 nospam3 sshd[540510]: Invalid user test from 134.122.56.104 port 41272
2026-02-11T17:16:25.588268+01:00 nospam3 sshd[540510]: Invalid user test from 134.122.56.104 port 41272
...
show less
Brute-Force
SSH
Anonymous
Feb 11 19:13:03 venus sshd[1996051]: Invalid user test from 134.122.56.104 port 45898
Feb 11 19:13:3 ...
show moreFeb 11 19:13:03 venus sshd[1996051]: Invalid user test from 134.122.56.104 port 45898
Feb 11 19:13:37 venus sshd[1996078]: Invalid user test from 134.122.56.104 port 44838
...
show less
Feb 11 17:12:34 jira sshd[291968]: Connection closed by invalid user test 134.122.56.104 port 38280 ...
show moreFeb 11 17:12:34 jira sshd[291968]: Connection closed by invalid user test 134.122.56.104 port 38280 [preauth]
Feb 11 17:13:03 jira sshd[291972]: Connection from 134.122.56.104 port 40962 on 138.201.123.138 port 22 rdomain ""
Feb 11 17:13:04 jira sshd[291972]: Invalid user test from 134.122.56.104 port 40962
Feb 11 17:13:04 jira sshd[291972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
Feb 11 17:13:06 jira sshd[291972]: Failed password for invalid user test from 134.122.56.104 port 40962 ssh2
...
show less
2026-02-11T18:06:54.589346+02:00 h03 sshd[620222]: Invalid user centos from 134.122.56.104 port 3547 ...
show more2026-02-11T18:06:54.589346+02:00 h03 sshd[620222]: Invalid user centos from 134.122.56.104 port 35470
2026-02-11T18:07:29.182936+02:00 h03 sshd[642498]: Invalid user centos from 134.122.56.104 port 58134
2026-02-11T18:08:03.812057+02:00 h03 sshd[662294]: Invalid user centos from 134.122.56.104 port 52334
2026-02-11T18:08:38.783742+02:00 h03 sshd[681411]: Invalid user centos from 134.122.56.104 port 49872
2026-02-11T18:09:13.707704+02:00 h03 sshd[704069]: Invalid user centos from 134.122.56.104 port 35962
...
show less
2026-02-11T16:02:30.301659+00:00 [REDACTED] sshd[474992]: Invalid user centos from 134.122.56.104 po ...
show more2026-02-11T16:02:30.301659+00:00 [REDACTED] sshd[474992]: Invalid user centos from 134.122.56.104 port 41950
2026-02-11T16:03:05.323952+00:00 [REDACTED] sshd[474994]: Invalid user centos from 134.122.56.104 port 36880
2026-02-11T16:03:38.952326+00:00 [REDACTED] sshd[475000]: Invalid user centos from 134.122.56.104 port 60558
2026-02-11T16:04:12.502828+00:00 [REDACTED] sshd[475005]: Invalid user centos from 134.122.56.104 port 37714
2026-02-11T16:04:46.504559+00:00 [REDACTED] sshd[475007]: Invalid user centos from 134.122.56.104 port 49812
show less
Feb 11 13:02:31 game-04 sshd[2123735]: Invalid user centos from 134.122.56.104 port 52460
Feb 11 13: ...
show moreFeb 11 13:02:31 game-04 sshd[2123735]: Invalid user centos from 134.122.56.104 port 52460
Feb 11 13:02:32 game-04 sshd[2123735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
Feb 11 13:02:33 game-04 sshd[2123735]: Failed password for invalid user centos from 134.122.56.104 port 52460 ssh2
Feb 11 13:02:32 game-04 sshd[2123735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
Feb 11 13:02:33 game-04 sshd[2123735]: Failed password for invalid user centos from 134.122.56.104 port 52460 ssh2
...
show less
Feb 11 15:53:54 instance-20241026-2018 sshd[393836]: Failed password for ubuntu from 134.122.56.104 ...
show moreFeb 11 15:53:54 instance-20241026-2018 sshd[393836]: Failed password for ubuntu from 134.122.56.104 port 50222 ssh2
Feb 11 15:54:28 instance-20241026-2018 sshd[393871]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104 user=ubuntu
Feb 11 15:54:30 instance-20241026-2018 sshd[393871]: Failed password for ubuntu from 134.122.56.104 port 43384 ssh2
Feb 11 15:55:04 instance-20241026-2018 sshd[393898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104 user=ubuntu
Feb 11 15:55:06 instance-20241026-2018 sshd[393898]: Failed password for ubuntu from 134.122.56.104 port 46362 ssh2
...
show less
2026-02-11T15:53:18.107729+00:00 vps-b43e0d3e sshd-session[3947706]: Failed password for invalid use ...
show more2026-02-11T15:53:18.107729+00:00 vps-b43e0d3e sshd-session[3947706]: Failed password for invalid user ubuntu from 134.122.56.104 port 53708 ssh2
2026-02-11T15:53:51.072376+00:00 vps-b43e0d3e sshd-session[3947747]: Invalid user ubuntu from 134.122.56.104 port 38938
2026-02-11T15:53:51.224968+00:00 vps-b43e0d3e sshd-session[3947747]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.56.104
2026-02-11T15:53:53.202049+00:00 vps-b43e0d3e sshd-session[3947747]: Failed password for invalid user ubuntu from 134.122.56.104 port 38938 ssh2
2026-02-11T15:54:26.874002+00:00 vps-b43e0d3e sshd-session[3947783]: Invalid user ubuntu from 134.122.56.104 port 36226
...
show less
Brute-Force
SSH
Showing 1 to
15
of 65 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩