This IP address has been reported a total of
214
times from
102 distinct
sources.
134.122.55.122 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.
2025-12-04T16:19:49.807337+01:00 meow sshd[1802775]: Invalid user jenkins from 134.122.55.122 port 4 ...
show more2025-12-04T16:19:49.807337+01:00 meow sshd[1802775]: Invalid user jenkins from 134.122.55.122 port 45482
2025-12-04T16:20:23.333622+01:00 meow sshd[1802791]: Invalid user jenkins from 134.122.55.122 port 56120
2025-12-04T16:20:59.380117+01:00 meow sshd[1802797]: Invalid user jenkins from 134.122.55.122 port 60684
2025-12-04T16:21:33.149346+01:00 meow sshd[1802809]: Invalid user jenkins from 134.122.55.122 port 47730
2025-12-04T16:22:04.696610+01:00 meow sshd[1802811]: Invalid user jenkins from 134.122.55.122 port 49078
...
show less
Dec 4 15:19:47 shomerdns sshd[441685]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ...
show moreDec 4 15:19:47 shomerdns sshd[441685]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
Dec 4 15:19:49 shomerdns sshd[441685]: Failed password for invalid user jenkins from 134.122.55.122 port 59446 ssh2
Dec 4 15:20:20 shomerdns sshd[441688]: Invalid user jenkins from 134.122.55.122 port 60274
show less
2025-12-04T17:18:18.111299+02:00 Node4-AMD sshd[1461245]: Invalid user tomcat from 134.122.55.122 po ...
show more2025-12-04T17:18:18.111299+02:00 Node4-AMD sshd[1461245]: Invalid user tomcat from 134.122.55.122 port 40468
...
show less
Dec 4 16:16:41 server sshd[1184624]: Failed password for invalid user tomcat from 134.122.55.122 po ...
show moreDec 4 16:16:41 server sshd[1184624]: Failed password for invalid user tomcat from 134.122.55.122 port 40210 ssh2
Dec 4 16:17:13 server sshd[1184653]: Invalid user tomcat from 134.122.55.122 port 42172
Dec 4 16:17:13 server sshd[1184653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
Dec 4 16:17:15 server sshd[1184653]: Failed password for invalid user tomcat from 134.122.55.122 port 42172 ssh2
Dec 4 16:17:46 server sshd[1184673]: Invalid user tomcat from 134.122.55.122 port 50818
...
show less
2025-12-04T17:14:07.702522+02:00 srv01 sshd-session[3718022]: Failed password for invalid user tomca ...
show more2025-12-04T17:14:07.702522+02:00 srv01 sshd-session[3718022]: Failed password for invalid user tomcat from 134.122.55.122 port 56376 ssh2
2025-12-04T17:14:40.013882+02:00 srv01 sshd-session[3718092]: Invalid user tomcat from 134.122.55.122 port 43732
2025-12-04T17:14:40.045716+02:00 srv01 sshd-session[3718092]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
2025-12-04T17:14:41.958439+02:00 srv01 sshd-session[3718092]: Failed password for invalid user tomcat from 134.122.55.122 port 43732 ssh2
2025-12-04T17:15:12.477145+02:00 srv01 sshd-session[3718163]: Invalid user tomcat from 134.122.55.122 port 47698
...
show less
Dec 4 16:16:22 Debian-1202-bookworm-amd64-base sshd[1263675]: Failed password for invalid user tomc ...
show moreDec 4 16:16:22 Debian-1202-bookworm-amd64-base sshd[1263675]: Failed password for invalid user tomcat from 134.122.55.122 port 50282 ssh2
Dec 4 16:16:54 Debian-1202-bookworm-amd64-base sshd[1278778]: Invalid user tomcat from 134.122.55.122 port 45426
Dec 4 16:16:54 Debian-1202-bookworm-amd64-base sshd[1278778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
Dec 4 16:16:56 Debian-1202-bookworm-amd64-base sshd[1278778]: Failed password for invalid user tomcat from 134.122.55.122 port 45426 ssh2
Dec 4 16:17:26 Debian-1202-bookworm-amd64-base sshd[1296144]: Invalid user tomcat from 134.122.55.122 port 46520
...
show less
Brute-Force
SSH
Anonymous
2025-12-04T18:16:11.945031+03:00 mike-Z390 sshd-session[2088488]: Failed password for invalid user t ...
show more2025-12-04T18:16:11.945031+03:00 mike-Z390 sshd-session[2088488]: Failed password for invalid user tomcat from 134.122.55.122 port 53606 ssh2
2025-12-04T18:16:43.868164+03:00 mike-Z390 sshd-session[2089960]: Invalid user tomcat from 134.122.55.122 port 40952
2025-12-04T18:16:44.101311+03:00 mike-Z390 sshd-session[2089960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
2025-12-04T18:16:45.524035+03:00 mike-Z390 sshd-session[2089960]: Failed password for invalid user tomcat from 134.122.55.122 port 40952 ssh2
2025-12-04T18:17:16.810385+03:00 mike-Z390 sshd-session[2091505]: Invalid user tomcat from 134.122.55.122 port 35698
...
show less
2025-12-04T16:16:01.553771+01:00 v2202509299507380972 sshd[1296958]: Failed password for invalid use ...
show more2025-12-04T16:16:01.553771+01:00 v2202509299507380972 sshd[1296958]: Failed password for invalid user tomcat from 134.122.55.122 port 49536 ssh2
2025-12-04T16:16:32.540769+01:00 v2202509299507380972 sshd[1297003]: Invalid user tomcat from 134.122.55.122 port 47560
2025-12-04T16:16:32.573890+01:00 v2202509299507380972 sshd[1297003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
2025-12-04T16:16:34.017085+01:00 v2202509299507380972 sshd[1297003]: Failed password for invalid user tomcat from 134.122.55.122 port 47560 ssh2
2025-12-04T16:17:06.364476+01:00 v2202509299507380972 sshd[1297059]: Invalid user tomcat from 134.122.55.122 port 48500
...
show less
Dec 4 16:15:16 unifi sshd[1319664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eui ...
show moreDec 4 16:15:16 unifi sshd[1319664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
Dec 4 16:15:18 unifi sshd[1319664]: Failed password for invalid user tomcat from 134.122.55.122 port 42686 ssh2
Dec 4 16:15:49 unifi sshd[1319686]: Invalid user tomcat from 134.122.55.122 port 55236
Dec 4 16:15:49 unifi sshd[1319686]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.55.122
Dec 4 16:15:51 unifi sshd[1319686]: Failed password for invalid user tomcat from 134.122.55.122 port 55236 ssh2
...
show less
2025-12-04T16:10:32.469937+01:00 orome sshd[3137136]: Invalid user dspace from 134.122.55.122 port 5 ...
show more2025-12-04T16:10:32.469937+01:00 orome sshd[3137136]: Invalid user dspace from 134.122.55.122 port 51348
2025-12-04T16:11:03.352659+01:00 orome sshd[3137317]: Invalid user dspace from 134.122.55.122 port 51884
2025-12-04T16:11:33.892906+01:00 orome sshd[3137353]: Invalid user dspace from 134.122.55.122 port 60484
2025-12-04T16:12:04.896281+01:00 orome sshd[3137508]: Invalid user dspace from 134.122.55.122 port 42270
2025-12-04T16:12:37.149224+01:00 orome sshd[3137547]: Invalid user dspace from 134.122.55.122 port 41928
...
show less
2025-12-04T17:09:48.899200+02:00 chnode1 sshd[2751700]: Invalid user dspace from 134.122.55.122 port ...
show more2025-12-04T17:09:48.899200+02:00 chnode1 sshd[2751700]: Invalid user dspace from 134.122.55.122 port 49224
2025-12-04T17:10:21.580032+02:00 chnode1 sshd[2759451]: Invalid user dspace from 134.122.55.122 port 55832
2025-12-04T17:10:52.469002+02:00 chnode1 sshd[2765611]: Invalid user dspace from 134.122.55.122 port 48108
2025-12-04T17:11:23.886907+02:00 chnode1 sshd[2772596]: Invalid user dspace from 134.122.55.122 port 35136
2025-12-04T17:11:54.302018+02:00 chnode1 sshd[2778761]: Invalid user dspace from 134.122.55.122 port 50616
...
show less
Brute-Force
SSH
Anonymous
2025-12-04T23:09:21.284671+08:00 netcup-nue-1 sshd[2379198]: Invalid user dspace from 134.122.55.122 ...
show more2025-12-04T23:09:21.284671+08:00 netcup-nue-1 sshd[2379198]: Invalid user dspace from 134.122.55.122 port 58596
...
show less
Dec 4 15:07:38 internal-mail-rafled-com sshd[620180]: Invalid user dspace from 134.122.55.122 port ...
show moreDec 4 15:07:38 internal-mail-rafled-com sshd[620180]: Invalid user dspace from 134.122.55.122 port 46938
...
show less
Brute-Force
SSH
Showing 1 to
15
of 214 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩