This IP address has been reported a total of
135
times from
125 distinct
sources.
34.38.136.18 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.
[bas-9] SSH abuse from 34.38.136.18: 9 x crowdsecurity/ssh-bf matched by the behaviour engine (autom ...
show more[bas-9] SSH abuse from 34.38.136.18: 9 x crowdsecurity/ssh-bf matched by the behaviour engine (automated sensor)
show less
SSH brute-force against an SSH honeypot: 1 credential attempt(s) across 1 logged events. Automated r ...
show moreSSH brute-force against an SSH honeypot: 1 credential attempt(s) across 1 logged events. Automated report from a Cowrie sensor.
show less
2026-08-26T08:30:03.797763+00:00 md sshd-session[2736252]: pam_unix(sshd:auth): authentication failu ...
show more2026-08-26T08:30:03.797763+00:00 md sshd-session[2736252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.38.136.18
2026-08-26T08:30:05.354474+00:00 md sshd-session[2736252]: Failed password for invalid user admin from 34.38.136.18 port 43594 ssh2
2026-08-26T08:30:08.847965+00:00 md sshd-session[2736252]: error: PAM: Authentication failure for illegal user admin from 34.38.136.18
2026-08-26T08:30:08.849454+00:00 md sshd-session[2736252]: Failed keyboard-interactive/pam for invalid user admin from 34.38.136.18 port 43594 ssh2
2026-08-26T08:30:08.895481+00:00 md sshd-session[2736252]: Connection closed by invalid user admin 34.38.136.18 port 43594 [preauth]
...
show less
2026-08-26T08:15:34.708783+00:00 sg-jumphost-server sshd[1293510]: Unable to negotiate with 34.38.13 ...
show more2026-08-26T08:15:34.708783+00:00 sg-jumphost-server sshd[1293510]: Unable to negotiate with 34.38.136.18 port 60628: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]
2026-08-26T08:15:35.302422+00:00 sg-jumphost-server sshd[1293509]: Invalid user hcbep from 34.38.136.18 port 60622
2026-08-26T08:15:35.470088+00:00 sg-jumphost-server sshd[1293509]: Connection closed by invalid user hcbep 34.38.136.18 port 60622 [preauth]
...
show less
2026-08-26T08:14:12.775172+01:00 akvorado sshd-session[518300]: Unable to negotiate with 34.38.136.1 ...
show more2026-08-26T08:14:12.775172+01:00 akvorado sshd-session[518300]: Unable to negotiate with 34.38.136.18 port 41422: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256 [preauth]
2026-08-26T08:14:13.047390+01:00 akvorado sshd-session[518329]: Unable to negotiate with 34.38.136.18 port 41426: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256 [preauth]
2026-08-26T08:14:13.581616+01:00 akvorado sshd-session[518335]: Unable to negotiate with 34.38.136.18 port 41458: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-
...
show less
Brute-Force
SSH
Showing 1 to
15
of 135 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩