This IP address has been reported a total of
92
times from
68 distinct
sources.
38.242.209.160 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-30T13:18:11.652162+02:00 Proxmox sshd-session[3617331]: Invalid user testuser from 38.242.20 ...
show more2026-06-30T13:18:11.652162+02:00 Proxmox sshd-session[3617331]: Invalid user testuser from 38.242.209.160 port 50820
2026-06-30T13:20:16.034722+02:00 Proxmox sshd-session[3618872]: Connection from 38.242.209.160 port 54882 on 142.132.206.185 port 22 rdomain ""
2026-06-30T13:20:16.205970+02:00 Proxmox sshd-session[3618872]: Invalid user es from 38.242.209.160 port 54882
...
show less
Jun 30 13:17:12 javastart sshd[361664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ...
show moreJun 30 13:17:12 javastart sshd[361664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160 user=root
Jun 30 13:17:14 javastart sshd[361664]: Failed password for root from 38.242.209.160 port 57170 ssh2
Jun 30 13:19:18 javastart sshd[361990]: Invalid user testuser from 38.242.209.160 port 36852
Jun 30 13:19:18 javastart sshd[361990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
Jun 30 13:19:20 javastart sshd[361990]: Failed password for invalid user testuser from 38.242.209.160 port 36852 ssh2
...
show less
2026-06-30T11:40:05.817731+01:00 ozelot sshd-session[4137330]: pam_unix(sshd:auth): authentication f ...
show more2026-06-30T11:40:05.817731+01:00 ozelot sshd-session[4137330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
2026-06-30T11:40:07.695697+01:00 ozelot sshd-session[4137330]: Failed password for invalid user cdp1 from 38.242.209.160 port 54946 ssh2
2026-06-30T11:44:08.863818+01:00 ozelot sshd-session[4188173]: Invalid user tick from 38.242.209.160 port 39240
show less
Jun 30 10:22:34 proxy-epyc sshd[4177588]: Failed password for invalid user alertus from 38.242.209.1 ...
show moreJun 30 10:22:34 proxy-epyc sshd[4177588]: Failed password for invalid user alertus from 38.242.209.160 port 46516 ssh2
Jun 30 10:26:39 proxy-epyc sshd[4178094]: Invalid user lucas from 38.242.209.160 port 58226
Jun 30 10:26:39 proxy-epyc sshd[4178094]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
Jun 30 10:26:41 proxy-epyc sshd[4178094]: Failed password for invalid user lucas from 38.242.209.160 port 58226 ssh2
Jun 30 10:28:39 proxy-epyc sshd[4178539]: Invalid user priem from 38.242.209.160 port 47984
...
show less
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2026-06-30T10:07:58Z and 2026-06- ...
show moreCowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2026-06-30T10:07:58Z and 2026-06-30T10:22:02Z
show less
2026-06-30T12:10:15.797685+02:00 Perseus sshd[1097227]: Invalid user profi from 38.242.209.160 port ...
show more2026-06-30T12:10:15.797685+02:00 Perseus sshd[1097227]: Invalid user profi from 38.242.209.160 port 52466
2026-06-30T12:10:15.802947+02:00 Perseus sshd[1097227]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
2026-06-30T12:10:17.499466+02:00 Perseus sshd[1097227]: Failed password for invalid user profi from 38.242.209.160 port 52466 ssh2
2026-06-30T12:12:16.615745+02:00 Perseus sshd[1098688]: Invalid user resolver from 38.242.209.160 port 36584
2026-06-30T12:12:16.620200+02:00 Perseus sshd[1098688]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
2026-06-30T12:12:18.261479+02:00 Perseus sshd[1098688]: Failed password for invalid user resolver from 38.242.209.160 port 36584 ssh2
2026-06-30T12:14:16.384899+02:00 Perseus sshd[1100127]: Invalid user zazcloud from 38.242.209.160 port 55534
...
show less
Jun 30 10:08:23 proxy-epyc sshd[4175373]: pam_unix(sshd:auth): authentication failure; logname= uid= ...
show moreJun 30 10:08:23 proxy-epyc sshd[4175373]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
Jun 30 10:08:25 proxy-epyc sshd[4175373]: Failed password for invalid user tsl from 38.242.209.160 port 45678 ssh2
Jun 30 10:12:22 proxy-epyc sshd[4175901]: Invalid user resolver from 38.242.209.160 port 51080
Jun 30 10:12:22 proxy-epyc sshd[4175901]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
Jun 30 10:12:24 proxy-epyc sshd[4175901]: Failed password for invalid user resolver from 38.242.209.160 port 51080 ssh2
...
show less
2026-06-30T06:01:56.611319-04:00 lg sshd[691422]: Failed password for invalid user mailgw from 38.24 ...
show more2026-06-30T06:01:56.611319-04:00 lg sshd[691422]: Failed password for invalid user mailgw from 38.242.209.160 port 49508 ssh2
2026-06-30T06:08:23.538681-04:00 lg sshd[691459]: Invalid user tsl from 38.242.209.160 port 55706
2026-06-30T06:08:23.546707-04:00 lg sshd[691459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
2026-06-30T06:08:25.870530-04:00 lg sshd[691459]: Failed password for invalid user tsl from 38.242.209.160 port 55706 ssh2
2026-06-30T06:10:18.059465-04:00 lg sshd[691524]: Invalid user profi from 38.242.209.160 port 45574
...
show less
2026-06-30T10:59:40.641709+01:00 ozelot sshd-session[3647763]: pam_unix(sshd:auth): authentication f ...
show more2026-06-30T10:59:40.641709+01:00 ozelot sshd-session[3647763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.242.209.160
2026-06-30T10:59:42.874054+01:00 ozelot sshd-session[3647763]: Failed password for invalid user mailgw from 38.242.209.160 port 43588 ssh2
2026-06-30T11:08:30.967063+01:00 ozelot sshd-session[3755163]: Invalid user tsl from 38.242.209.160 port 33378
show less
Brute-Force
SSH
Showing 1 to
15
of 92 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩