Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
174.138.80.165 has been reported 46
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.
Mar 5 20:12:21 dev sshd[1603718]: Invalid user weblogic from 174.138.80.165 port 37892
Mar 5 20:14:45 dev sshd[1603760]: Invalid user apache from 174.138.80.165 port 44470
Mar 5 20:15:51 dev sshd[1604137]: Invalid user postgres from 174.138.80.165 ...
show moreMar 5 20:12:21 dev sshd[1603718]: Invalid user weblogic from 174.138.80.165 port 37892
Mar 5 20:14:45 dev sshd[1603760]: Invalid user apache from 174.138.80.165 port 44470
Mar 5 20:15:51 dev sshd[1604137]: Invalid user postgres from 174.138.80.165 port 57134
Mar 5 20:17:09 dev sshd[1604176]: Invalid user postgres from 174.138.80.165 port 38314
Mar 5 20:18:38 dev sshd[1604213]: Invalid user postgres from 174.138.80.165 port 59920
...
show less
2026-03-05T18:15:21.234928 DE-NB-1 sshd[60010]: Failed password for invalid user apache from 174.138.80.165 port 60136 ssh2
2026-03-05T18:16:27.156619 DE-NB-1 sshd[60036]: Invalid user postgres from 174.138.80.165 port 44200
2026-03-05T18:16:27.38336 ...
show more2026-03-05T18:15:21.234928 DE-NB-1 sshd[60010]: Failed password for invalid user apache from 174.138.80.165 port 60136 ssh2
2026-03-05T18:16:27.156619 DE-NB-1 sshd[60036]: Invalid user postgres from 174.138.80.165 port 44200
2026-03-05T18:16:27.383361 DE-NB-1 sshd[60036]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.80.165
2026-03-05T18:16:29.708140 DE-NB-1 sshd[60036]: Failed password for invalid user postgres from 174.138.80.165 port 44200 ssh2
2026-03-05T18:17:58.408432 DE-NB-1 sshd[60058]: Invalid user postgres from 174.138.80.165 port 42350
...
show less
2026-03-05T18:13:13.331296+00:00 2.4c4f56loss.net sshd-session[1279419]: Invalid user weblogic from 174.138.80.165 port 56332
2026-03-05T18:14:21.015565+00:00 2.4c4f56loss.net sshd-session[1289449]: Invalid user mysql from 174.138.80.165 port 37452
2 ...
show more2026-03-05T18:13:13.331296+00:00 2.4c4f56loss.net sshd-session[1279419]: Invalid user weblogic from 174.138.80.165 port 56332
2026-03-05T18:14:21.015565+00:00 2.4c4f56loss.net sshd-session[1289449]: Invalid user mysql from 174.138.80.165 port 37452
2026-03-05T18:15:30.954065+00:00 2.4c4f56loss.net sshd-session[1300289]: Invalid user apache from 174.138.80.165 port 59342
...
show less
2026-03-05T18:07:23.261829 vpn-admin.cgi-labs.de sshd[4040510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.80.165
2026-03-05T18:07:24.905110 vpn-admin.cgi-labs.de sshd[4040510]: Failed password for ...
show more2026-03-05T18:07:23.261829 vpn-admin.cgi-labs.de sshd[4040510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.80.165
2026-03-05T18:07:24.905110 vpn-admin.cgi-labs.de sshd[4040510]: Failed password for invalid user git from 174.138.80.165 port 55990 ssh2
2026-03-05T18:07:23.261829 vpn-admin.cgi-labs.de sshd[4040510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.80.165
2026-03-05T18:07:24.905110 vpn-admin.cgi-labs.de sshd[4040510]: Failed password for invalid user git from 174.138.80.165 port 55990 ssh2
2026-03-05T18:08:28.516685 vpn-admin.cgi-labs.de sshd[4040526]: Invalid user deploy from 174.138.80.165 port 41378
...
show less
Brute-Force
SSH
Anonymous
Mar 5 17:57:22 newbrook-two sshd[363753]: Invalid user postgres from 174.138.80.165 port 40708
Mar 5 17:58:42 newbrook-two sshd[364159]: Invalid user oracle from 174.138.80.165 port 59194
Mar 5 17:59:59 newbrook-two sshd[364530]: Invalid user user ...
show moreMar 5 17:57:22 newbrook-two sshd[363753]: Invalid user postgres from 174.138.80.165 port 40708
Mar 5 17:58:42 newbrook-two sshd[364159]: Invalid user oracle from 174.138.80.165 port 59194
Mar 5 17:59:59 newbrook-two sshd[364530]: Invalid user user from 174.138.80.165 port 60688
Mar 5 18:01:17 newbrook-two sshd[364915]: Invalid user vps from 174.138.80.165 port 43902
Mar 5 18:02:43 newbrook-two sshd[365321]: Invalid user testuser from 174.138.80.165 port 47572
...
show less
2026-03-05T18:57:03.056777+01:00 [REDACTED] sshd[122526]: Invalid user postgres from 174.138.80.165 port 48360
2026-03-05T18:58:27.970474+01:00 [REDACTED] sshd[122552]: Invalid user oracle from 174.138.80.165 port 59708
2026-03-05T18:59:42.894230+01: ...
show more2026-03-05T18:57:03.056777+01:00 [REDACTED] sshd[122526]: Invalid user postgres from 174.138.80.165 port 48360
2026-03-05T18:58:27.970474+01:00 [REDACTED] sshd[122552]: Invalid user oracle from 174.138.80.165 port 59708
2026-03-05T18:59:42.894230+01:00 [REDACTED] sshd[122595]: Invalid user user from 174.138.80.165 port 42146
2026-03-05T19:00:57.335390+01:00 [REDACTED] sshd[122608]: Invalid user vps from 174.138.80.165 port 36200
2026-03-05T19:02:20.757894+01:00 [REDACTED] sshd[122628]: Invalid user testuser from 174.138.80.165 port 49924
show less
Brute-Force
SSH
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown