This IP address has been reported a total of
83
times from
58 distinct
sources.
134.199.149.122 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.
Automated SSH brute-force attack detected. The IP repeatedly attempted to authenticate to port 22 us ...
show moreAutomated SSH brute-force attack detected. The IP repeatedly attempted to authenticate to port 22 using multiple usernames and password guesses within a short timeframe.
show less
2026-03-17T10:29:10.135811+00:00 prod-westeu sshd[1055839]: Invalid user postgres from 134.199.149.1 ...
show more2026-03-17T10:29:10.135811+00:00 prod-westeu sshd[1055839]: Invalid user postgres from 134.199.149.122 port 57190
2026-03-17T10:29:10.912160+00:00 prod-westeu sshd[1055839]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.149.122
2026-03-17T10:29:12.826171+00:00 prod-westeu sshd[1055839]: Failed password for invalid user postgres from 134.199.149.122 port 57190 ssh2
...
show less
Mar 17 11:26:56 zurich-2 sshd[2135838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ...
show moreMar 17 11:26:56 zurich-2 sshd[2135838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.149.122 user=root
Mar 17 11:26:58 zurich-2 sshd[2135838]: Failed password for root from 134.199.149.122 port 58758 ssh2
Mar 17 11:29:10 zurich-2 sshd[2135878]: Invalid user postgres from 134.199.149.122 port 51162
...
show less
Illegal access attempt:2026-03-17T11:27:04.304817+01:00 xn--kster-juait sshd[3331668]: Failed passwo ...
show moreIllegal access attempt:2026-03-17T11:27:04.304817+01:00 xn--kster-juait sshd[3331668]: Failed password for root from 134.199.149.122 port 60620 ssh2
2026-03-17T11:27:06.026867+01:00 xn--kster-juait sshd[3331668]: error: maximum authentication attempts exceeded for root from 134.199.149.122 port 60620 ssh2 [preauth]
...
show less
2026-03-13T18:34:30.181680+01:00 eproxy sshd[261662]: Invalid user centos from 134.199.149.122 port ...
show more2026-03-13T18:34:30.181680+01:00 eproxy sshd[261662]: Invalid user centos from 134.199.149.122 port 53154
2026-03-13T18:35:35.648644+01:00 eproxy sshd[261692]: Invalid user centos from 134.199.149.122 port 49776
...
show less
2026-03-13T20:33:29.207325pantelemone.ru sshd[213637]: pam_unix(sshd:auth): authentication failure; ...
show more2026-03-13T20:33:29.207325pantelemone.ru sshd[213637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.149.122
2026-03-13T20:33:31.673221pantelemone.ru sshd[213637]: Failed password for invalid user centos from 134.199.149.122 port 47488 ssh2
2026-03-13T20:34:31.027177pantelemone.ru sshd[213722]: Invalid user centos from 134.199.149.122 port 33514
2026-03-13T20:34:31.342335pantelemone.ru sshd[213722]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.149.122
2026-03-13T20:34:32.985367pantelemone.ru sshd[213722]: Failed password for invalid user centos from 134.199.149.122 port 33514 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 83 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩