This IP address has been reported a total of
162
times from
146 distinct
sources.
116.99.168.34 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.
Suricata Detected 378 attacks from 116.99.168.34.; ET SCAN Potential SSH Scan; IP: 116.99.168.34; Po ...
show moreSuricata Detected 378 attacks from 116.99.168.34.; ET SCAN Potential SSH Scan; IP: 116.99.168.34; Ports: 50932; Direction: to_server; Trigger: SCAN; Category: Attempted Information Leak; Severity: 2
show less
Detected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: honeypot_ssh. So ...
show moreDetected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: honeypot_ssh. Sources: honeypot. First seen: 2026-07-02. Risk score: 100/100.
show less
2026-07-02T17:30:36.213029+03:00 gc1 sshd[4123691]: Failed password for invalid user admin from 116. ...
show more2026-07-02T17:30:36.213029+03:00 gc1 sshd[4123691]: Failed password for invalid user admin from 116.99.168.34 port 33254 ssh2
2026-07-02T17:30:54.582542+03:00 gc1 sshd[4123693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.168.34 user=root
2026-07-02T17:30:56.006131+03:00 gc1 sshd[4123693]: Failed password for root from 116.99.168.34 port 42544 ssh2
...
show less
2026-07-02T16:17:03.941024+02:00 crma sshd[2372384]: Invalid user support from 116.99.168.34 port 54 ...
show more2026-07-02T16:17:03.941024+02:00 crma sshd[2372384]: Invalid user support from 116.99.168.34 port 54044
2026-07-02T16:17:55.756095+02:00 crma sshd[2373157]: Invalid user guest from 116.99.168.34 port 55522
2026-07-02T16:18:41.862548+02:00 crma sshd[2373422]: Invalid user admin from 116.99.168.34 port 35092
2026-07-02T16:24:09.460645+02:00 crma sshd[2377354]: Invalid user operator from 116.99.168.34 port 49188
2026-07-02T16:26:12.869127+02:00 crma sshd[2378721]: Invalid user admin from 116.99.168.34 port 56438
...
show less
Brute-Force
SSH
Anonymous
$f2bV_matches
Brute-Force
SSH
Anonymous
Jul 2 17:14:46 dev sshd[304838]: Invalid user installer from 116.99.168.34 port 50238
Jul 2 17:14: ...
show moreJul 2 17:14:46 dev sshd[304838]: Invalid user installer from 116.99.168.34 port 50238
Jul 2 17:14:54 dev sshd[304840]: Invalid user squid from 116.99.168.34 port 55076
Jul 2 17:18:23 dev sshd[305282]: Invalid user system from 116.99.168.34 port 35294
Jul 2 17:20:14 dev sshd[305693]: Invalid user admin from 116.99.168.34 port 39128
Jul 2 17:25:13 dev sshd[305782]: Invalid user nikita from 116.99.168.34 port 55938
...
show less
Fail2ban sshd: 2026-07-02T14:17:06.248940+00:00 siem-test sshd[3400056]: Failed password for invalid ...
show moreFail2ban sshd: 2026-07-02T14:17:06.248940+00:00 siem-test sshd[3400056]: Failed password for invalid user squid from 116.99.168.34 port 36702 ssh2
2026-07-02T14:17:19.457087+00:00 siem-test sshd[3400152]: Invalid user installer from 116.99.168.34 port 59678
2026-07-02T14:19:42.695817+00:00 siem-test sshd[3400209]: Invalid user system from 116.99.168.34 port 50856
2026-07-02T14:24:35.524958+00:00 siem-test sshd[3400639]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116
show less
Brute-Force
SSH
Anonymous
2026-07-02T16:17:03.431086+02:00 HETZNER-FI-1 sshd[4112173]: Invalid user support from 116.99.168.34 ...
show more2026-07-02T16:17:03.431086+02:00 HETZNER-FI-1 sshd[4112173]: Invalid user support from 116.99.168.34 port 34856
2026-07-02T16:23:12.413598+02:00 HETZNER-FI-1 sshd[4143966]: Invalid user admin from 116.99.168.34 port 48416
2026-07-02T16:23:39.712292+02:00 HETZNER-FI-1 sshd[4147050]: Invalid user operator from 116.99.168.34 port 42014
...
show less