This IP address has been reported a total of
194
times from
123 distinct
sources.
134.122.54.118 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-01-29T15:36:23.219752 host sshd[706428]: Connection closed by 134.122.54.118 port 50512 2026-01 ...
show more2026-01-29T15:36:23.219752 host sshd[706428]: Connection closed by 134.122.54.118 port 50512 2026-01-29T15:43:32.680533 host sshd[706434]: user XXXX from 134.122.54.118 not allowed because not listed in AllowUsers 2026-01-29T15:44:15.590518 host sshd[706438]: Connection closed by invalid user root 134.122.54.118 port 34514 [preauth]
show less
Honeypot hit: Brute-force attack detected on 22/SSH
โข Number of sessions: 3
โข Credentials: root:1234 ...
show moreHoneypot hit: Brute-force attack detected on 22/SSH
โข Number of sessions: 3
โข Credentials: root:123456, root:password
โข Number of login attempts: 2
โข Client: SSH-2.0-Go
show less
2026-01-29T08:21:23.411893+01:00 ubuntu sshd-session[150408]: Failed password for invalid user user ...
show more2026-01-29T08:21:23.411893+01:00 ubuntu sshd-session[150408]: Failed password for invalid user user from 134.122.54.118 port 53326 ssh2
2026-01-29T08:21:43.010813+01:00 ubuntu sshd-session[150410]: Invalid user user from 134.122.54.118 port 49998
2026-01-29T08:21:43.067180+01:00 ubuntu sshd-session[150410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.54.118
2026-01-29T08:21:44.955507+01:00 ubuntu sshd-session[150410]: Failed password for invalid user user from 134.122.54.118 port 49998 ssh2
2026-01-29T08:22:05.845962+01:00 ubuntu sshd-session[150426]: Invalid user user from 134.122.54.118 port 54686
...
show less
2026-01-29T07:59:38.595798+01:00 ubuntu sshd-session[150070]: pam_unix(sshd:auth): authentication fa ...
show more2026-01-29T07:59:38.595798+01:00 ubuntu sshd-session[150070]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.54.118
2026-01-29T07:59:41.147619+01:00 ubuntu sshd-session[150070]: Failed password for invalid user postgres from 134.122.54.118 port 54768 ssh2
2026-01-29T08:00:02.412030+01:00 ubuntu sshd-session[150092]: Invalid user postgres from 134.122.54.118 port 52332
2026-01-29T08:00:02.539497+01:00 ubuntu sshd-session[150092]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.54.118
2026-01-29T08:00:04.577405+01:00 ubuntu sshd-session[150092]: Failed password for invalid user postgres from 134.122.54.118 port 52332 ssh2
...
show less
Jan 29 07:36:51 office sshd[3734219]: Invalid user test1 from 134.122.54.118 port 41142
Jan 29 07:38 ...
show moreJan 29 07:36:51 office sshd[3734219]: Invalid user test1 from 134.122.54.118 port 41142
Jan 29 07:38:12 office sshd[3734227]: Invalid user test2 from 134.122.54.118 port 35300
Jan 29 07:38:49 office sshd[3734237]: Invalid user test3 from 134.122.54.118 port 57332
Jan 29 07:43:08 office sshd[3734268]: Invalid user postgres from 134.122.54.118 port 36964
Jan 29 07:43:35 office sshd[3734272]: Invalid user oracle from 134.122.54.118 port 43654
show less
Brute-Force
SSH
Showing 1 to
15
of 194 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown ๐ฉ