This IP address has been reported a total of
1,154
times from
707 distinct
sources.
116.99.172.104 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.
Reporter
IoA Timestamp (UTC)
Comment
Categories
Anonymous
Phishing and smtprelay and use of leaked account data
Hacking
Anonymous
Fail2ban (sshd jail): 2 failed SSH attempts from 116.99.172.104.
Jul 8 21:42:03 vps789833 sshd[21551]: Failed password for root from 116.99.172.104 port 39810 ssh2
...
show moreJul 8 21:42:03 vps789833 sshd[21551]: Failed password for root from 116.99.172.104 port 39810 ssh2
Jul 8 21:44:11 vps789833 sshd[21577]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.172.104
Jul 8 21:44:13 vps789833 sshd[21577]: Failed password for invalid user support from 116.99.172.104 port 46706 ssh2
show less
116.99.172.104 fell into Endlessh tarpit; 0/36 total connections are currently still open. Total tim ...
show more116.99.172.104 fell into Endlessh tarpit; 0/36 total connections are currently still open. Total time wasted: 1h 5m 55s. Total bytes sent by tarpit: 489.00KiB. Report generated by Endlessh Report Generator v1.2.3
show less
Detected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: fail2ban_ban. So ...
show moreDetected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: fail2ban_ban. Sources: fail2ban. First seen: 2026-07-08. Risk score: 20/100.
show less
Failed password for root Jul 08 21:41:21 port 39498
Brute-Force
SSH
Anonymous
2026-07-08 22:20:52,611 fail2ban.actions [515047]: NOTICE [sshd] Ban 116.99.172.104
2026-07- ...
show more2026-07-08 22:20:52,611 fail2ban.actions [515047]: NOTICE [sshd] Ban 116.99.172.104
2026-07-08 22:31:10,080 fail2ban.actions [515047]: NOTICE [sshd] Ban 116.99.172.104
...
show less
2026-07-08T20:25:15.918822+00:00 vpn-tor sshd[1825012]: Invalid user support from 116.99.172.104 por ...
show more2026-07-08T20:25:15.918822+00:00 vpn-tor sshd[1825012]: Invalid user support from 116.99.172.104 port 54684
2026-07-08T20:25:14.389754+00:00 vpn-tor sshd[1824990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.172.104 user=root
2026-07-08T20:25:17.066183+00:00 vpn-tor sshd[1824990]: Failed password for root from 116.99.172.104 port 54442 ssh2
2026-07-08T20:25:16.151153+00:00 vpn-tor sshd[1825012]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.172.104
2026-07-08T20:25:18.099546+00:00 vpn-tor sshd[1825012]: Failed password for invalid user support from 116.99.172.104 port 54684 ssh2
...
show less
2026-07-08T20:21:12.613939+00:00 enklol sshd-session[3461856]: Invalid user ubnt from 116.99.172.104 ...
show more2026-07-08T20:21:12.613939+00:00 enklol sshd-session[3461856]: Invalid user ubnt from 116.99.172.104 port 41210
2026-07-08T20:21:29.487280+00:00 enklol sshd-session[3461874]: Invalid user installer from 116.99.172.104 port 39452
2026-07-08T20:21:38.856734+00:00 enklol sshd-session[3461884]: Invalid user admin from 116.99.172.104 port 53230
2026-07-08T20:21:58.671722+00:00 enklol sshd-session[3461888]: Invalid user user from 116.99.172.104 port 51238
2026-07-08T20:24:35.427843+00:00 enklol sshd-session[3461970]: Invalid user config from 116.99.172.104 port 33950
...
show less
Brute-Force
SSH
Showing 1 to
15
of 1154 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩