This IP address has been reported a total of
55
times from
53 distinct
sources.
116.99.170.54 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.
2026-06-29T15:26:41.038118+02:00 chnode1 sshd[3353697]: Invalid user user from 116.99.170.54 port 48 ...
show more2026-06-29T15:26:41.038118+02:00 chnode1 sshd[3353697]: Invalid user user from 116.99.170.54 port 48666
2026-06-29T15:26:58.180505+02:00 chnode1 sshd[3357420]: Invalid user ubnt from 116.99.170.54 port 58686
2026-06-29T15:27:05.989707+02:00 chnode1 sshd[3359304]: Invalid user guest from 116.99.170.54 port 54796
2026-06-29T15:27:35.469564+02:00 chnode1 sshd[3365839]: Invalid user admin from 116.99.170.54 port 37466
2026-06-29T15:27:47.472050+02:00 chnode1 sshd[3367701]: Invalid user ftp from 116.99.170.54 port 40538
...
show less
2026-06-29T13:26:47.397614+00:00 [host] sshd[579584]: Invalid user ubnt from 116.99.170.54 port 3903 ...
show more2026-06-29T13:26:47.397614+00:00 [host] sshd[579584]: Invalid user ubnt from 116.99.170.54 port 39032
2026-06-29T13:26:58.635838+00:00 [host] sshd[579593]: Invalid user test from 116.99.170.54 port 36402
2026-06-29T13:27:10.439067+00:00 [host] sshd[579597]: Invalid user operator from 116.99.170.54 port 56264
show less
2026-06-29T15:26:53.054209+02:00 perseus sshd-session[3539012]: Failed password for invalid user sys ...
show more2026-06-29T15:26:53.054209+02:00 perseus sshd-session[3539012]: Failed password for invalid user system from 116.99.170.54 port 44684 ssh2
2026-06-29T15:27:00.090612+02:00 perseus sshd-session[3539017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.170.54 user=root
2026-06-29T15:27:02.299722+02:00 perseus sshd-session[3539017]: Failed password for root from 116.99.170.54 port 57946 ssh2
show less
2026-06-29T13:05:39.515563+00:00 wp20241125 sshd[375087]: Invalid user system from 116.99.170.54 por ...
show more2026-06-29T13:05:39.515563+00:00 wp20241125 sshd[375087]: Invalid user system from 116.99.170.54 port 50280
2026-06-29T13:05:51.717458+00:00 wp20241125 sshd[375091]: Invalid user squid from 116.99.170.54 port 58270
2026-06-29T13:05:55.469052+00:00 wp20241125 sshd[375093]: Invalid user guest from 116.99.170.54 port 49538
2026-06-29T13:06:19.631422+00:00 wp20241125 sshd[375095]: Invalid user test from 116.99.170.54 port 33466
2026-06-29T13:06:23.824902+00:00 wp20241125 sshd[375102]: Invalid user user from 116.99.170.54 port 36856
...
show less
2026-06-29T15:04:51.475985+02:00 1.api.chattedrooms.com sshd[3736909]: Invalid user admin from 116.9 ...
show more2026-06-29T15:04:51.475985+02:00 1.api.chattedrooms.com sshd[3736909]: Invalid user admin from 116.99.170.54 port 33270
2026-06-29T15:05:29.079170+02:00 1.api.chattedrooms.com sshd[3736942]: Invalid user admin from 116.99.170.54 port 51460
2026-06-29T15:05:49.806989+02:00 1.api.chattedrooms.com sshd[3736965]: User root not allowed because account is locked
2026-06-29T15:05:50.040545+02:00 1.api.chattedrooms.com sshd[3736965]: Connection closed by invalid user root 116.99.170.54 port 33036 [preauth]
2026-06-29T15:05:55.584610+02:00 1.api.chattedrooms.com sshd[3737013]: Invalid user test from 116.99.170.54 port 42088
...
show less
Brute-Force
SSH
Showing 1 to
15
of 55 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩