This IP address has been reported a total of
395
times from
217 distinct
sources.
213.131.64.123 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.
Jul 3 17:07:15 instance1 sshd[704874]: Disconnected from authenticating user root 213.131.64.123 po ...
show moreJul 3 17:07:15 instance1 sshd[704874]: Disconnected from authenticating user root 213.131.64.123 port 44900 [preauth]
...
show less
Jul 2 03:35:52 uptime-kuma sshd[3871562]: Disconnected from authenticating user root 213.131.64.123 ...
show moreJul 2 03:35:52 uptime-kuma sshd[3871562]: Disconnected from authenticating user root 213.131.64.123 port 38170 [preauth]
...
show less
2026-06-28T04:29:05.764999+00:00 thelemmy.club sshd-session[32986]: Invalid user natalia from 213.13 ...
show more2026-06-28T04:29:05.764999+00:00 thelemmy.club sshd-session[32986]: Invalid user natalia from 213.131.64.123 port 47582
2026-06-28T04:29:05.904740+00:00 thelemmy.club sshd-session[32986]: Disconnected from invalid user natalia 213.131.64.123 port 47582 [preauth]
...
show less
Jun 27 18:53:34 b146-68 sshd[37838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eui ...
show moreJun 27 18:53:34 b146-68 sshd[37838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.131.64.123
Jun 27 18:53:36 b146-68 sshd[37838]: Failed password for invalid user foundry from 213.131.64.123 port 46362 ssh2
Jun 27 19:15:36 b146-68 sshd[38090]: Invalid user srv from 213.131.64.123 port 50724
...
show less
SSH Brute force: 6 attempts were recorded from 213.131.64.123
2026-06-27T20:21:31+02:00 Invalid user ...
show moreSSH Brute force: 6 attempts were recorded from 213.131.64.123
2026-06-27T20:21:31+02:00 Invalid user db2 from 213.131.64.123 port 56146
2026-06-27T20:44:03+02:00 Disconnected from authenticating user root 213.131.64.123 port 42324 [preauth]
2026-06-27T20:45:52+02:00 User nobody from 213.131.64.123 not allowed because none of user's groups are listed in AllowGroups
2026-06-27T20:46:09+02:00 Invalid user jeus from 213.131.64.123 port 48046
2026-06-27T20:47:36+02:00 Invalid user user from 213.131.64.123 port 56866
2026-06-27T20:47:48+02:00 Invalid user yxu from 213.131.64.123 port 55634
show less
SSH Brute force: 1 attempts were recorded from 213.131.64.123
2026-06-26T05:45:31+02:00 Invalid user ...
show moreSSH Brute force: 1 attempts were recorded from 213.131.64.123
2026-06-26T05:45:31+02:00 Invalid user election from 213.131.64.123 port 54620
show less
Jun 24 19:15:14 b146-67 sshd[435268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eu ...
show moreJun 24 19:15:14 b146-67 sshd[435268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.131.64.123
Jun 24 19:15:16 b146-67 sshd[435268]: Failed password for invalid user temp from 213.131.64.123 port 53058 ssh2
Jun 24 19:24:56 b146-67 sshd[435360]: Invalid user viewer from 213.131.64.123 port 33032
...
show less
2026-06-24T17:19:28.932349+00:00 powarnitzynalexander5.serv.host sshd-session[32293]: Invalid user g ...
show more2026-06-24T17:19:28.932349+00:00 powarnitzynalexander5.serv.host sshd-session[32293]: Invalid user gfs from 213.131.64.123 port 35044
...
show less
Brute-Force
SSH
Showing 1 to
15
of 395 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩