This IP address has been reported a total of
330
times from
203 distinct
sources.
38.104.95.242 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.
Reporter
IoA Timestamp (UTC)
Comment
Categories
Anonymous
2026-07-17T17:16:05.033405+02:00 7802 sshd[82933]: pam_unix(sshd:auth): authentication failure; logn ...
show more2026-07-17T17:16:05.033405+02:00 7802 sshd[82933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-17T17:16:07.856596+02:00 7802 sshd[82933]: Failed password for invalid user cw from 38.104.95.242 port 10421 ssh2
2026-07-17T17:16:47.082170+02:00 7802 sshd[83096]: Invalid user www from 38.104.95.242 port 10422
2026-07-17T17:16:47.232779+02:00 7802 sshd[83096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-17T17:16:49.488501+02:00 7802 sshd[83096]: Failed password for invalid user www from 38.104.95.242 port 10422 ssh2
...
show less
Jul 17 17:11:08 jira sshd[3915849]: Connection closed by invalid user admin1 38.104.95.242 port 1042 ...
show moreJul 17 17:11:08 jira sshd[3915849]: Connection closed by invalid user admin1 38.104.95.242 port 10423 [preauth]
Jul 17 17:11:15 jira sshd[3915853]: Connection from 38.104.95.242 port 10424 on 138.201.123.138 port 22 rdomain ""
Jul 17 17:11:15 jira sshd[3915853]: Invalid user fivem from 38.104.95.242 port 10424
Jul 17 17:11:15 jira sshd[3915853]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
Jul 17 17:11:17 jira sshd[3915853]: Failed password for invalid user fivem from 38.104.95.242 port 10424 ssh2
...
show less
Brute-Force
SSH
Anonymous
2026-07-17T16:49:33.846351+02:00 7802 sshd[75399]: pam_unix(sshd:auth): authentication failure; logn ...
show more2026-07-17T16:49:33.846351+02:00 7802 sshd[75399]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242 user=root
2026-07-17T16:49:35.445506+02:00 7802 sshd[75399]: Failed password for root from 38.104.95.242 port 10401 ssh2
2026-07-17T16:50:04.087381+02:00 7802 sshd[75563]: Invalid user trader from 38.104.95.242 port 10402
2026-07-17T16:50:04.239842+02:00 7802 sshd[75563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-17T16:50:06.094558+02:00 7802 sshd[75563]: Failed password for invalid user trader from 38.104.95.242 port 10402 ssh2
...
show less
Jul 17 16:48:17 jira sshd[3915509]: Connection from 38.104.95.242 port 10400 on 138.201.123.138 port ...
show moreJul 17 16:48:17 jira sshd[3915509]: Connection from 38.104.95.242 port 10400 on 138.201.123.138 port 22 rdomain ""
Jul 17 16:48:18 jira sshd[3915509]: Invalid user elasticsearch from 38.104.95.242 port 10400
Jul 17 16:48:18 jira sshd[3915509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
Jul 17 16:48:20 jira sshd[3915509]: Failed password for invalid user elasticsearch from 38.104.95.242 port 10400 ssh2
Jul 17 16:48:21 jira sshd[3915509]: Connection closed by invalid user elasticsearch 38.104.95.242 port 10400 [preauth]
...
show less
2026-07-16T17:18:33.706258+05:30 nms sshd[1940395]: Failed password for invalid user sonar from 38.1 ...
show more2026-07-16T17:18:33.706258+05:30 nms sshd[1940395]: Failed password for invalid user sonar from 38.104.95.242 port 10400 ssh2
2026-07-16T17:18:38.328133+05:30 nms sshd[1940397]: Invalid user zabbix from 38.104.95.242 port 10401
2026-07-16T17:18:38.580401+05:30 nms sshd[1940397]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-16T17:18:41.100123+05:30 nms sshd[1940397]: Failed password for invalid user zabbix from 38.104.95.242 port 10401 ssh2
2026-07-16T17:18:43.589091+05:30 nms sshd[1940399]: Invalid user edward from 38.104.95.242 port 10402
...
show less
2026-07-16T12:47:59.574433+01:00 s0 sshd[556883]: pam_unix(sshd:auth): authentication failure; logna ...
show more2026-07-16T12:47:59.574433+01:00 s0 sshd[556883]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-16T12:48:01.737992+01:00 s0 sshd[556883]: Failed password for invalid user admin2 from 38.104.95.242 port 10400 ssh2
2026-07-16T12:48:03.025073+01:00 s0 sshd[556891]: Invalid user amir from 38.104.95.242 port 10401
...
show less
Observed automated SSH brute-force activity.
Attempts: 12 | Failed password: 6 | Invalid user: 6
Fir ...
show moreObserved automated SSH brute-force activity.
Attempts: 12 | Failed password: 6 | Invalid user: 6
First seen: 2026-07-15 13:53:43 UTC
Last seen: 2026-07-15 14:02:51 UTC
Source: Linux OpenSSH journalctl telemetry from OVH-hosted Debian server.
show less
Brute-Force
SSH
Anonymous
2026-07-15T16:01:51.454087 prodgateway sshd-session[9875]: Invalid user backup from 38.104.95.242 po ...
show more2026-07-15T16:01:51.454087 prodgateway sshd-session[9875]: Invalid user backup from 38.104.95.242 port 10400
2026-07-15T16:01:51.566173 prodgateway sshd-session[9875]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.104.95.242
2026-07-15T16:01:53.833722 prodgateway sshd-session[9875]: Failed password for invalid user backup from 38.104.95.242 port 10400 ssh2
...
show less