This IP address has been reported a total of
205
times from
106 distinct
sources.
104.253.134.62 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.
[markis] Auto banned by Fail2Ban. Reason: SSH brute force / repeated failed login attempts. Evidence ...
show more[markis] Auto banned by Fail2Ban. Reason: SSH brute force / repeated failed login attempts. Evidence:
2026-07-19T22:51:27.845273+00:00 sshd-session[334524]: Invalid user user1 from 104.253.134.62 port 33682
2026-07-19T22:51:27.848528+00:00 sshd-session[334524]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.253.134.62
2026-07-19T22:51:29.626065+00:00 sshd-session[334524]: Failed password for invalid user user1 from 104.253.134.62 port 33682 ssh2
2026-07-19T22:54:09.634901+00:00 sshd-session[334574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.253.134.62 user=root
2026-07-19T22:54:11.277955+00:00 sshd-session[334574]: Failed password for root from 104.253.134.62 port 58384 ssh2
show less
SSH brute-force attempt detected from IP 104.253.134.62: 2026-07-19T22:47:32.725694+00:00 [redacted- ...
show moreSSH brute-force attempt detected from IP 104.253.134.62: 2026-07-19T22:47:32.725694+00:00 [redacted-hostname] sshd[1728599]: Failed password for invalid user test from 104.253.134.62 port 42600 ssh2 on 1784501635.
show less
2026-07-19T22:45:46.771Z, an unauthorized access attempt was detected on port 22 (SSH) from source I ...
show more2026-07-19T22:45:46.771Z, an unauthorized access attempt was detected on port 22 (SSH) from source IP address 104.253.134.62.
show less
2026-07-20T01:28:50.746054+03:00 proxy-msk1 sshd[3127313]: Invalid user ubuntu from 104.253.134.62 p ...
show more2026-07-20T01:28:50.746054+03:00 proxy-msk1 sshd[3127313]: Invalid user ubuntu from 104.253.134.62 port 32942
2026-07-20T01:28:50.750819+03:00 proxy-msk1 sshd[3127313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.253.134.62
2026-07-20T01:28:52.546973+03:00 proxy-msk1 sshd[3127313]: Failed password for invalid user ubuntu from 104.253.134.62 port 32942 ssh2
2026-07-20T01:31:30.015620+03:00 proxy-msk1 sshd[3127390]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.253.134.62 user=root
2026-07-20T01:31:31.973331+03:00 proxy-msk1 sshd[3127390]: Failed password for root from 104.253.134.62 port 48772 ssh2
show less
2026-07-20T07:28:22.860833+09:00 iesaba sshd[135411]: Invalid user user1 from 104.253.134.62 port 48 ...
show more2026-07-20T07:28:22.860833+09:00 iesaba sshd[135411]: Invalid user user1 from 104.253.134.62 port 48316
2026-07-20T07:31:01.691507+09:00 iesaba sshd[135433]: Invalid user ubuntu from 104.253.134.62 port 35014
...
show less
2026-07-20T07:07:11.645006+09:00 iesaba sshd[135021]: Invalid user composer from 104.253.134.62 port ...
show more2026-07-20T07:07:11.645006+09:00 iesaba sshd[135021]: Invalid user composer from 104.253.134.62 port 43014
2026-07-20T07:12:31.651969+09:00 iesaba sshd[135161]: Invalid user centos from 104.253.134.62 port 41244
...
show less
Brute-Force
SSH
Showing 1 to
15
of 205 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩