Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
43.138.164.13 has been reported 95
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
This IP address carried out 40 SSH credential attack (attempts) between 21-04-2023 to 15-05-2023. For more information or to report interesting/incorrect findings, give me a shoutout @parthmaniar on Twitter.
May 7 03:47:17 regorland sshd[23056]: Invalid user user from 43.138.164.13 port 35688
May 7 03:47:19 regorland sshd[23119]: Connection from 43.138.164.13 port 35740 on 15.235.53.99 port 22 rdomain ""
May 7 03:47:20 regorland sshd[23119]: Invalid u ...
show moreMay 7 03:47:17 regorland sshd[23056]: Invalid user user from 43.138.164.13 port 35688
May 7 03:47:19 regorland sshd[23119]: Connection from 43.138.164.13 port 35740 on 15.235.53.99 port 22 rdomain ""
May 7 03:47:20 regorland sshd[23119]: Invalid user testuser from 43.138.164.13 port 35740
...
show less
May 6 22:59:25 hosting sshd[35698]: Invalid user admin from 43.138.164.13 port 49328
May 6 22:59:25 hosting sshd[35708]: Invalid user nagios from 43.138.164.13 port 49336
May 6 22:59:25 hosting sshd[35711]: Invalid user service from 43.138.164.13 ...
show moreMay 6 22:59:25 hosting sshd[35698]: Invalid user admin from 43.138.164.13 port 49328
May 6 22:59:25 hosting sshd[35708]: Invalid user nagios from 43.138.164.13 port 49336
May 6 22:59:25 hosting sshd[35711]: Invalid user service from 43.138.164.13 port 49342
May 6 22:59:25 hosting sshd[35707]: Invalid user user from 43.138.164.13 port 49324
May 6 22:59:25 hosting sshd[35702]: Invalid user hadoop from 43.138.164.13 port 49296
...
show less
Lines containing failures of 43.138.164.13 (max 1000)
May 3 04:08:07 v11 sshd[174722]: Connection closed by 43.138.164.13 port 57234
May 3 04:08:08 v11 sshd[1050]: drop connection #17 from [43.138.164.13]:34984 on [46.182.23.101]:22 past MaxStartup ...
show moreLines containing failures of 43.138.164.13 (max 1000)
May 3 04:08:07 v11 sshd[174722]: Connection closed by 43.138.164.13 port 57234
May 3 04:08:08 v11 sshd[1050]: drop connection #17 from [43.138.164.13]:34984 on [46.182.23.101]:22 past MaxStartups
May 3 04:08:08 v11 sshd[174737]: User r.r from 43.138.164.13 not allowed because not listed in AllowUsers
May 3 04:08:08 v11 sshd[174740]: AD user linuxadmin from 43.138.164.13 port 34986
May 3 04:08:08 v11 sshd[174745]: AD user user1 from 43.138.164.13 port 34974
May 3 04:08:08 v11 sshd[174752]: AD user jenkins from 43.138.164.13 port 34992
May 3 04:08:09 v11 sshd[174745]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.138.164.13
May 3 04:08:09 v11 sshd[174737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.138.164.13 user=r.r
May 3 04:08:09 v11 sshd[174752]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 t........
------------------------------
show less
Lines containing failures of 43.138.164.13 (max 1000)
May 3 04:08:07 v11 sshd[174722]: Connection closed by 43.138.164.13 port 57234
May 3 04:08:08 v11 sshd[1050]: drop connection #17 from [43.138.164.13]:34984 on [46.182.23.101]:22 past MaxStartup ...
show moreLines containing failures of 43.138.164.13 (max 1000)
May 3 04:08:07 v11 sshd[174722]: Connection closed by 43.138.164.13 port 57234
May 3 04:08:08 v11 sshd[1050]: drop connection #17 from [43.138.164.13]:34984 on [46.182.23.101]:22 past MaxStartups
May 3 04:08:08 v11 sshd[174737]: User r.r from 43.138.164.13 not allowed because not listed in AllowUsers
May 3 04:08:08 v11 sshd[174740]: AD user linuxadmin from 43.138.164.13 port 34986
May 3 04:08:08 v11 sshd[174745]: AD user user1 from 43.138.164.13 port 34974
May 3 04:08:08 v11 sshd[174752]: AD user jenkins from 43.138.164.13 port 34992
May 3 04:08:09 v11 sshd[174745]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.138.164.13
May 3 04:08:09 v11 sshd[174737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.138.164.13 user=r.r
May 3 04:08:09 v11 sshd[174752]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 t........
------------------------------
show less
2023-05-06T14:37:52.896542server2.ebullit.com sshd[4649]: Invalid user admin from 43.138.164.13 port 53596
2023-05-06T14:37:52.956712server2.ebullit.com sshd[4647]: Invalid user postgres from 43.138.164.13 port 53576
2023-05-06T14:37:53.089293server2 ...
show more2023-05-06T14:37:52.896542server2.ebullit.com sshd[4649]: Invalid user admin from 43.138.164.13 port 53596
2023-05-06T14:37:52.956712server2.ebullit.com sshd[4647]: Invalid user postgres from 43.138.164.13 port 53576
2023-05-06T14:37:53.089293server2.ebullit.com sshd[4654]: Invalid user postgres from 43.138.164.13 port 53566
2023-05-06T14:37:53.089548server2.ebullit.com sshd[4653]: Invalid user server from 43.138.164.13 port 53584
2023-05-06T14:37:53.122883server2.ebullit.com sshd[4644]: Invalid user ansible from 43.138.164.13 port 53570
...
show less
May 6 18:49:33 bongen-tmp-rt.local sshd[2659618]: Invalid user user from 43.138.164.13 port 37320
May 6 18:49:33 bongen-tmp-rt.local sshd[2659619]: Invalid user ansible from 43.138.164.13 port 37300
May 6 18:49:33 bongen-tmp-rt.local sshd[2659625] ...
show moreMay 6 18:49:33 bongen-tmp-rt.local sshd[2659618]: Invalid user user from 43.138.164.13 port 37320
May 6 18:49:33 bongen-tmp-rt.local sshd[2659619]: Invalid user ansible from 43.138.164.13 port 37300
May 6 18:49:33 bongen-tmp-rt.local sshd[2659625]: Invalid user postgres from 43.138.164.13 port 37296
May 6 18:49:33 bongen-tmp-rt.local sshd[2659629]: Invalid user fa from 43.138.164.13 port 37370
May 6 18:49:34 bongen-tmp-rt.local sshd[2659618]: Connection closed by invalid user user 43.138.164.13 port 37320 [preauth]
show less
May 6 18:49:33 bongen-tmp-rt.local sshd[2659618]: Invalid user user from 43.138.164.13 port 37320
May 6 18:49:33 bongen-tmp-rt.local sshd[2659619]: Invalid user ansible from 43.138.164.13 port 37300
May 6 18:49:33 bongen-tmp-rt.local sshd[2659625] ...
show moreMay 6 18:49:33 bongen-tmp-rt.local sshd[2659618]: Invalid user user from 43.138.164.13 port 37320
May 6 18:49:33 bongen-tmp-rt.local sshd[2659619]: Invalid user ansible from 43.138.164.13 port 37300
May 6 18:49:33 bongen-tmp-rt.local sshd[2659625]: Invalid user postgres from 43.138.164.13 port 37296
May 6 18:49:33 bongen-tmp-rt.local sshd[2659629]: Invalid user fa from 43.138.164.13 port 37370
May 6 18:49:34 bongen-tmp-rt.local sshd[2659618]: Connection closed by invalid user user 43.138.164.13 port 37320 [preauth]
show less
Brute-Force
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown