This IP address has been reported a total of
246
times from
126 distinct
sources.
134.122.59.52 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
2025-11-23T05:29:02.104659+08:00 bird sshd[1129537]: Failed password for invalid user ec2-user from ...
show more2025-11-23T05:29:02.104659+08:00 bird sshd[1129537]: Failed password for invalid user ec2-user from 134.122.59.52 port 60146 ssh2
2025-11-23T05:29:22.125532+08:00 bird sshd[1129541]: Invalid user ec2-user from 134.122.59.52 port 60758
2025-11-23T05:29:22.555900+08:00 bird sshd[1129541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
2025-11-23T05:29:24.761045+08:00 bird sshd[1129541]: Failed password for invalid user ec2-user from 134.122.59.52 port 60758 ssh2
2025-11-23T05:29:37.040609+08:00 bird sshd[1129547]: Invalid user ec2-user from 134.122.59.52 port 35834
...
show less
2025-11-22T23:27:52.589368+02:00 FDC sshd[2411546]: pam_unix(sshd:auth): authentication failure; log ...
show more2025-11-22T23:27:52.589368+02:00 FDC sshd[2411546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
2025-11-22T23:27:55.440237+02:00 FDC sshd[2411546]: Failed password for invalid user ec2-user from 134.122.59.52 port 57860 ssh2
2025-11-22T23:28:28.333554+02:00 FDC sshd[2413117]: Invalid user ec2-user from 134.122.59.52 port 41296
...
show less
Nov 22 21:26:50 host sshd[459574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid= ...
show moreNov 22 21:26:50 host sshd[459574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
Nov 22 21:26:51 host sshd[459574]: Failed password for invalid user pi from 134.122.59.52 port 55804 ssh2
Nov 22 21:27:28 host sshd[459583]: Invalid user ec2-user from 134.122.59.52 port 44630
Nov 22 21:27:28 host sshd[459583]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
Nov 22 21:27:30 host sshd[459583]: Failed password for invalid user ec2-user from 134.122.59.52 port 44630 ssh2
...
show less
Nov 22 22:24:38 pinomail sshd[2959345]: Invalid user pi from 134.122.59.52 port 37430
Nov 22 22:25:1 ...
show moreNov 22 22:24:38 pinomail sshd[2959345]: Invalid user pi from 134.122.59.52 port 37430
Nov 22 22:25:16 pinomail sshd[2964407]: Invalid user pi from 134.122.59.52 port 43682
Nov 22 22:25:53 pinomail sshd[2967961]: Invalid user pi from 134.122.59.52 port 59840
Nov 22 22:26:31 pinomail sshd[2972692]: Invalid user pi from 134.122.59.52 port 53048
Nov 22 22:27:09 pinomail sshd[2977926]: Invalid user ec2-user from 134.122.59.52 port 46054
...
show less
2025-11-22T22:26:46.505516+01:00 ryzen-vm-big sshd[2358265]: pam_unix(sshd:auth): authentication fai ...
show more2025-11-22T22:26:46.505516+01:00 ryzen-vm-big sshd[2358265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
2025-11-22T22:26:49.295980+01:00 ryzen-vm-big sshd[2358265]: Failed password for invalid user pi from 134.122.59.52 port 46166 ssh2
...
show less
Nov 22 22:26:42 amk sshd\[30562\]: Invalid user pi from 134.122.59.52Nov 22 22:26:44 amk sshd\[30562 ...
show moreNov 22 22:26:42 amk sshd\[30562\]: Invalid user pi from 134.122.59.52Nov 22 22:26:44 amk sshd\[30562\]: Failed password for invalid user pi from 134.122.59.52 port 52334 ssh2
...
show less
2025-11-22T22:25:03.333546+01:00 dnsguard-dedi sshd[3312833]: Failed password for invalid user pi fr ...
show more2025-11-22T22:25:03.333546+01:00 dnsguard-dedi sshd[3312833]: Failed password for invalid user pi from 134.122.59.52 port 57020 ssh2
2025-11-22T22:25:37.920760+01:00 dnsguard-dedi sshd[3313254]: Invalid user pi from 134.122.59.52 port 49098
2025-11-22T22:25:37.982041+01:00 dnsguard-dedi sshd[3313254]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
2025-11-22T22:25:39.965970+01:00 dnsguard-dedi sshd[3313254]: Failed password for invalid user pi from 134.122.59.52 port 49098 ssh2
2025-11-22T22:26:16.002837+01:00 dnsguard-dedi sshd[3313735]: Invalid user pi from 134.122.59.52 port 50342
...
show less
2025-11-22T22:24:59.110783+01:00 vmi2893862 sshd-session[1378039]: Failed password for invalid user ...
show more2025-11-22T22:24:59.110783+01:00 vmi2893862 sshd-session[1378039]: Failed password for invalid user pi from 134.122.59.52 port 48524 ssh2
2025-11-22T22:25:34.088717+01:00 vmi2893862 sshd-session[1385132]: Invalid user pi from 134.122.59.52 port 34308
2025-11-22T22:25:34.217242+01:00 vmi2893862 sshd-session[1385132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.59.52
2025-11-22T22:25:36.434301+01:00 vmi2893862 sshd-session[1385132]: Failed password for invalid user pi from 134.122.59.52 port 34308 ssh2
2025-11-22T22:26:12.856169+01:00 vmi2893862 sshd-session[1394047]: Invalid user pi from 134.122.59.52 port 41950
...
show less
Brute-Force
SSH
Showing 1 to
15
of 246 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩