This IP address has been reported a total of
97
times from
70 distinct
sources.
138.201.172.203 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.
Jun 11 11:30:18 hosting sshd[152084]: Invalid user bitcoin from 138.201.172.203 port 58488
Jun 11 11 ...
show moreJun 11 11:30:18 hosting sshd[152084]: Invalid user bitcoin from 138.201.172.203 port 58488
Jun 11 11:30:18 hosting sshd[152084]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.201.172.203
Jun 11 11:30:19 hosting sshd[152084]: Failed password for invalid user bitcoin from 138.201.172.203 port 58488 ssh2
show less
Jun 11 14:27:41 rapi wings[1730548]: WARN: [Jun 11 14:27:41.845] failed to validate user credentials ...
show moreJun 11 14:27:41 rapi wings[1730548]: WARN: [Jun 11 14:27:41.845] failed to validate user credentials (invalid format) ip=138.201.172.203:38150 method=password subsystem=sftp username=root
Jun 11 14:27:42 rapi wings[1730548]: ERROR: [Jun 11 14:27:42.032] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=138.201.172.203:38150
show less
(sshd) Failed SSH login from 138.201.172.203 (DE/Germany/static.203.172.201.138.clients.your-server. ...
show more(sshd) Failed SSH login from 138.201.172.203 (DE/Germany/static.203.172.201.138.clients.your-server.de)
show less
Fail2Ban found 2026-06-11T03:10:47.195504+00:00 node1 sshd[2750831]: pam_unix(sshd:auth): authentica ...
show moreFail2Ban found 2026-06-11T03:10:47.195504+00:00 node1 sshd[2750831]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.201.172.203
2026-06-11T03:10:49.010475+00:00 node1 sshd[2750831]: Failed password for invalid user crypto from 138.201.172.203 port 53258 ssh2
2026-06-11T03:38:17.179569+00:00 node1 sshd[2751488]: Invalid user deploy from 138.201.172.203 port 37528 attempts
show less
[EmExpress] Auto banned by Fail2Ban. Reason: SSH brute force / repeated failed login attempts. Evide ...
show more[EmExpress] Auto banned by Fail2Ban. Reason: SSH brute force / repeated failed login attempts. Evidence:
Jun 11 02:30:41 emexpress sshd[234430]: Failed password for root from 138.201.172.203 port 46762 ssh2
Jun 11 02:31:39 emexpress sshd[234440]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.201.172.203 user=root
Jun 11 02:31:41 emexpress sshd[234440]: Failed password for root from 138.201.172.203 port 41290 ssh2
show less
Brute-Force
SSH
Showing 1 to
15
of 97 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩