This IP address has been reported a total of
53
times from
50 distinct
sources.
134.122.29.213 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.
2026-08-30T20:34:52.839593shield sshd\[21539\]: Invalid user sol from 134.122.29.213 port 56576
2026 ...
show more2026-08-30T20:34:52.839593shield sshd\[21539\]: Invalid user sol from 134.122.29.213 port 56576
2026-08-30T20:34:52.845436shield sshd\[21539\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.29.213
2026-08-30T20:34:54.607769shield sshd\[21539\]: Failed password for invalid user sol from 134.122.29.213 port 56576 ssh2
2026-08-30T20:40:11.068257shield sshd\[22567\]: Invalid user sol from 134.122.29.213 port 35996
2026-08-30T20:40:11.079143shield sshd\[22567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.29.213
show less
2026-08-30T20:24:00.715362+00:00 instance-20250416-2306 sshd-session[3924896]: Invalid user paladin ...
show more2026-08-30T20:24:00.715362+00:00 instance-20250416-2306 sshd-session[3924896]: Invalid user paladin from 134.122.29.213 port 45256
2026-08-30T20:26:26.149526+00:00 instance-20250416-2306 sshd-session[3924905]: Invalid user sol from 134.122.29.213 port 60106
2026-08-30T20:29:02.429494+00:00 instance-20250416-2306 sshd-session[3924910]: Invalid user sol from 134.122.29.213 port 51832
2026-08-30T20:31:39.861865+00:00 instance-20250416-2306 sshd-session[3924915]: Invalid user sol from 134.122.29.213 port 38086
2026-08-30T20:34:11.878304+00:00 instance-20250416-2306 sshd-session[3924923]: Invalid user sol from 134.122.29.213 port 47274
...
show less
2026-08-31T04:28:57.442763+08:00 *hostname* sshd-session[110002]: Invalid user sol from 134.122.29.2 ...
show more2026-08-31T04:28:57.442763+08:00 *hostname* sshd-session[110002]: Invalid user sol from 134.122.29.213 port 55936
2026-08-31T04:31:34.230941+08:00 *hostname* sshd-session[110014]: Connection from 134.122.29.213 port 53014 on 10.0.0.24 port 22 rdomain ""
2026-08-31T04:31:34.958017+08:00 *hostname* sshd-session[110014]: Invalid user sol from 134.122.29.213 port 53014
2026-08-31T04:34:06.428753+08:00 *hostname* sshd-session[110026]: Connection from 134.122.29.213 port 44486 on 10.0.0.24 port 22 rdomain ""
2026-08-31T04:34:07.135126+08:00 *hostname* sshd-session[110026]: Invalid user sol from 134.122.29.213 port 44486
show less
2026-08-31T08:23:46.551139+12:00 localhost sshd[1770096]: Invalid user paladin from 134.122.29.213 p ...
show more2026-08-31T08:23:46.551139+12:00 localhost sshd[1770096]: Invalid user paladin from 134.122.29.213 port 50294
2026-08-31T08:26:12.120023+12:00 localhost sshd[1772016]: Invalid user sol from 134.122.29.213 port 34338
2026-08-31T08:28:47.506549+12:00 localhost sshd[1774025]: Invalid user sol from 134.122.29.213 port 42336
2026-08-31T08:31:25.172451+12:00 localhost sshd[1775967]: Invalid user sol from 134.122.29.213 port 34020
2026-08-31T08:33:58.043513+12:00 localhost sshd[1777635]: Invalid user sol from 134.122.29.213 port 48326
show less
Detected multiple authentication failures and invalid user attempts from IP address 134.122.29.213 o ...
show moreDetected multiple authentication failures and invalid user attempts from IP address 134.122.29.213 on [PT] Lis-3 Node.
show less
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