This IP address has been reported a total of
3,550
times from
848 distinct
sources.
138.68.180.134 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.
Sep 3 12:53:56 b146-04 sshd[442194]: Invalid user genusredis from 138.68.180.134 port 52418
Sep 3 ...
show moreSep 3 12:53:56 b146-04 sshd[442194]: Invalid user genusredis from 138.68.180.134 port 52418
Sep 3 12:53:56 b146-04 sshd[442194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.180.134
Sep 3 12:53:58 b146-04 sshd[442194]: Failed password for invalid user genusredis from 138.68.180.134 port 52418 ssh2
...
show less
Sep 3 15:55:44 de-fra2-dns2 sshd[43880]: Invalid user sysman from 138.68.180.134 port 57214
Sep 3 ...
show moreSep 3 15:55:44 de-fra2-dns2 sshd[43880]: Invalid user sysman from 138.68.180.134 port 57214
Sep 3 15:58:26 de-fra2-dns2 sshd[43909]: Invalid user chris from 138.68.180.134 port 48226
Sep 3 16:01:11 de-fra2-dns2 sshd[44239]: Invalid user tt from 138.68.180.134 port 36708
...
show less
Sep 4 01:23:07 ms2 sshd[40206]: Invalid user sysman from 138.68.180.134 port 48556
Sep 4 01:28:17 ...
show moreSep 4 01:23:07 ms2 sshd[40206]: Invalid user sysman from 138.68.180.134 port 48556
Sep 4 01:28:17 ms2 sshd[42211]: Invalid user chris from 138.68.180.134 port 49270
...
show less
Sep 3 08:04:51 nyc sshd[225517]: Invalid user lij from 138.68.180.134 port 42944
Sep 3 08:05:48 ny ...
show moreSep 3 08:04:51 nyc sshd[225517]: Invalid user lij from 138.68.180.134 port 42944
Sep 3 08:05:48 nyc sshd[225521]: Invalid user sne from 138.68.180.134 port 34878
Sep 3 08:10:33 nyc sshd[225546]: Invalid user jzh from 138.68.180.134 port 43966
Sep 3 08:11:30 nyc sshd[225552]: Invalid user msger from 138.68.180.134 port 48694
Sep 3 08:13:29 nyc sshd[225558]: Invalid user bryan from 138.68.180.134 port 33074
...
show less
Sep 3 07:43:07 nyc sshd[225372]: Invalid user mare from 138.68.180.134 port 57484
Sep 3 07:51:46 n ...
show moreSep 3 07:43:07 nyc sshd[225372]: Invalid user mare from 138.68.180.134 port 57484
Sep 3 07:51:46 nyc sshd[225409]: Invalid user wangpf from 138.68.180.134 port 50594
Sep 3 07:52:38 nyc sshd[225414]: Invalid user lighthouse from 138.68.180.134 port 51394
Sep 3 07:53:30 nyc sshd[225418]: Invalid user edi from 138.68.180.134 port 40992
Sep 3 07:54:27 nyc sshd[225424]: Invalid user airlab from 138.68.180.134 port 55866
...
show less
2024-09-03T13:09:59.264718 socky.stom66.co.uk sshd[821202]: Invalid user frontend from 138.68.180.13 ...
show more2024-09-03T13:09:59.264718 socky.stom66.co.uk sshd[821202]: Invalid user frontend from 138.68.180.134 port 45992
2024-09-03T13:17:02.373542 socky.stom66.co.uk sshd[822647]: Invalid user zd from 138.68.180.134 port 59030
...
show less
Sep 3 11:38:27 vpn sshd[2282199]: Failed password for root from 138.68.180.134 port 39982 ssh2
Sep ...
show moreSep 3 11:38:27 vpn sshd[2282199]: Failed password for root from 138.68.180.134 port 39982 ssh2
Sep 3 11:44:28 vpn sshd[2282279]: Invalid user servidor from 138.68.180.134 port 44306
...
show less
Brute-Force
SSH
Anonymous
2024-09-03T19:10:15.551435+08:00 ocLObk1008638 sshd[3077361]: Invalid user javad from 138.68.180.134 ...
show more2024-09-03T19:10:15.551435+08:00 ocLObk1008638 sshd[3077361]: Invalid user javad from 138.68.180.134 port 50998
2024-09-03T19:15:44.316181+08:00 ocLObk1008638 sshd[3077463]: Invalid user sftp_user from 138.68.180.134 port 46856
2024-09-03T19:16:29.862250+08:00 ocLObk1008638 sshd[3077475]: Invalid user susanne from 138.68.180.134 port 49348
2024-09-03T19:19:04.671422+08:00 ocLObk1008638 sshd[3077547]: Invalid user kiosk from 138.68.180.134 port 48984
...
show less
Brute-Force
SSH
Showing 1 to
15
of 3550 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩