This IP address has been reported a total of
137
times from
104 distinct
sources.
116.110.80.138 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.
2025-04-01T19:46:58.686278-06:00 plex sshd[266975]: Connection closed by 116.110.80.138 port 39146 [ ...
show more2025-04-01T19:46:58.686278-06:00 plex sshd[266975]: Connection closed by 116.110.80.138 port 39146 [preauth]
2025-04-01T19:46:58.712163-06:00 plex sshd[266981]: Connection closed by 116.110.80.138 port 58838 [preauth]
2025-04-01T19:46:58.716931-06:00 plex sshd[266969]: Connection closed by 116.110.80.138 port 37904 [preauth]
...
show less
Mar 31 20:45:29 manchegosr sshd[3324597]: Invalid user squid from 116.110.80.138 port 36246
Mar 31 2 ...
show moreMar 31 20:45:29 manchegosr sshd[3324597]: Invalid user squid from 116.110.80.138 port 36246
Mar 31 20:46:21 manchegosr sshd[3324624]: Invalid user installer from 116.110.80.138 port 49696
Mar 31 20:46:43 manchegosr sshd[3324744]: Invalid user ubnt from 116.110.80.138 port 39104
...
show less
Mar 31 20:45:45 hardcore-tesla sshd[2376419]: pam_unix(sshd:auth): authentication failure; logname= ...
show moreMar 31 20:45:45 hardcore-tesla sshd[2376419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.80.138
Mar 31 20:45:47 hardcore-tesla sshd[2376419]: Failed password for invalid user admin from 116.110.80.138 port 58972 ssh2
Mar 31 20:46:09 hardcore-tesla sshd[2376423]: Invalid user config from 116.110.80.138 port 49636
Mar 31 20:46:09 hardcore-tesla sshd[2376423]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.80.138
Mar 31 20:46:11 hardcore-tesla sshd[2376423]: Failed password for invalid user config from 116.110.80.138 port 49636 ssh2
...
show less
2025-03-31T21:44:58.104657+01:00 bcn01-es-pop.as202427.net sshd[1366982]: User root from 116.110.80. ...
show more2025-03-31T21:44:58.104657+01:00 bcn01-es-pop.as202427.net sshd[1366982]: User root from 116.110.80.138 not allowed because not listed in AllowUsers
2025-03-31T21:45:43.189749+01:00 bcn01-es-pop.as202427.net sshd[1367067]: Invalid user config from 116.110.80.138 port 34550
2025-03-31T21:45:47.008808+01:00 bcn01-es-pop.as202427.net sshd[1367059]: Invalid user admin from 116.110.80.138 port 34548
...
show less
Brute-Force
SSH
Anonymous
Mar 31 22:45:25 C1D543E sshd[2078423]: User root from 116.110.80.138 not allowed because not listed ...
show moreMar 31 22:45:25 C1D543E sshd[2078423]: User root from 116.110.80.138 not allowed because not listed in AllowUsers
Mar 31 22:45:25 C1D543E sshd[2078423]: Failed password for invalid user root from 116.110.80.138 port 46184 ssh2
Mar 31 22:45:36 C1D543E sshd[2078427]: Invalid user user from 116.110.80.138 port 55940
Mar 31 22:45:37 C1D543E sshd[2078427]: Failed password for invalid user user from 116.110.80.138 port 55940 ssh2
Mar 31 22:45:42 C1D543E sshd[2078429]: User root from 116.110.80.138 not allowed because not listed in AllowUsers
...
show less
Report 1657867 with IP 2705420 for SSH brute-force attack by source 2700092 via ssh-honeypot/0.2.0+h ...
show moreReport 1657867 with IP 2705420 for SSH brute-force attack by source 2700092 via ssh-honeypot/0.2.0+http
show less
Brute-Force
SSH
Showing 1 to
15
of 137 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩