This IP address has been reported a total of
121
times from
105 distinct
sources.
35.195.137.4 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-08-26T12:06:50.646144+03:00 phenom sshd-session[5892]: Invalid user admin from 35.195.137.4 por ...
show more2026-08-26T12:06:50.646144+03:00 phenom sshd-session[5892]: Invalid user admin from 35.195.137.4 port 29836
2026-08-26T12:06:50.744686+03:00 phenom ss
...
show less
2026-08-26T10:38:55.133539+02:00 muse sshd-session[1972118]: Invalid user uvnrc from 35.195.137.4 po ...
show more2026-08-26T10:38:55.133539+02:00 muse sshd-session[1972118]: Invalid user uvnrc from 35.195.137.4 port 10606
...
show less
Unauthorized connection attempt detected from IP address 35.195.137.4 to port 22 (banankicks-server) ...
show moreUnauthorized connection attempt detected from IP address 35.195.137.4 to port 22 (banankicks-server) [x]
show less
SSH honeypot detection (Endlessh tarpit, port 22). 29 probe(s) sustained for 9m total hold time. 1 K ...
show moreSSH honeypot detection (Endlessh tarpit, port 22). 29 probe(s) sustained for 9m total hold time. 1 KB of synthetic SSH banner data served to exhaust attacker resources. Consistent with automated SSH scanning/brute-force. Reported by dotnetdork.dev security honeypot.
show less
2026-08-26T09:27:42.338105+02:00 pbs-ovh sshd-session[438339]: refused connect from 4.137.195.35.bc. ...
show more2026-08-26T09:27:42.338105+02:00 pbs-ovh sshd-session[438339]: refused connect from 4.137.195.35.bc.googleusercontent.com (35.195.137.4) 2026-08-26T09:27:47.546019+02:00 pbs-ovh sshd-session[438399]: refused connect from 4.137.195.35.bc.googleusercontent.com (35.195.137.4) 2026-08-26T09:27:49.364688+02:00 pbs-ovh sshd-session[438402]: refused connect from 4.137.195.35.bc.googleusercontent.com (35.195.137.4)
show less
2026-08-26T07:27:32.796593+00:00 singularity3 sshd[89385]: Unable to negotiate with 35.195.137.4 por ...
show more2026-08-26T07:27:32.796593+00:00 singularity3 sshd[89385]: Unable to negotiate with 35.195.137.4 port 18730: no matching host key type found. Their offer: ssh-dss [preauth]
2026-08-26T07:27:33.065139+00:00 singularity3 sshd[89387]: Unable to negotiate with 35.195.137.4 port 18742: no matching host key type found. Their offer: ssh-rsa [preauth]
2026-08-26T07:27:33.539922+00:00 singularity3 sshd[89389]: Connection closed by 35.195.137.4 port 18754 [preauth]
2026-08-26T07:27:33.705018+00:00 singularity3 sshd[89391]: Unable to negotiate with 35.195.137.4 port 18762: no matching host key type found. Their offer: ecdsa-sha2-nistp384 [preauth]
2026-08-26T07:27:33.968744+00:00 singularity3 sshd[89393]: Unable to negotiate with 35.195.137.4 port 18774: no matching host key type found. Their offer: ecdsa-sha2-nistp521 [preauth]
...
show less
Aug 26 07:27:07 instance-20221219-1303 sshd[416647]: Invalid user mywbv from 35.195.137.4 port 49286 ...
show moreAug 26 07:27:07 instance-20221219-1303 sshd[416647]: Invalid user mywbv from 35.195.137.4 port 49286
...
show less
2026-08-26T10:24:38.648194+03:00 instance460168.waicore.network sshd-session[12264]: Invalid user ad ...
show more2026-08-26T10:24:38.648194+03:00 instance460168.waicore.network sshd-session[12264]: Invalid user admin from 35.195.137.4 port 46002
...
show less
SSH brute-force attempt from 35.195.137.4 blocked by Houston-Xeon-Dartnode. 2026-08-26T07:23:28.7930 ...
show moreSSH brute-force attempt from 35.195.137.4 blocked by Houston-Xeon-Dartnode. 2026-08-26T07:23:28.793029+00:00 texas.dartnode.com sshd[3128383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.195.137.4
2026-08-26T07:23:31.303208+00:00 texas.dartnode.com sshd[3128383]: Failed password for invalid user admin from 35.195.137.4 port 53792 ssh2
2026-08-26T07:23:32.189140+00:00 texas.dartnode.com sshd[3128383]: Connection closed by invalid user admin 35.195.137.4 port 53792 [preauth]
show less