This IP address has been reported a total of
41
times from
38 distinct
sources.
34.140.148.49 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-09-02T05:35:00.033056+02:00 thor sshd-session[542793]: Unable to negotiate with 34.140.148.49 p ...
show more2026-09-02T05:35:00.033056+02:00 thor sshd-session[542793]: Unable to negotiate with 34.140.148.49 port 29166: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]
2026-09-02T05:35:10.738503+02:00 thor sshd-session[542795]: Invalid user qffpr from 34.140.148.49 port 52188
2026-09-02T05:35:10.837900+02:00 thor sshd-session[542795]: Connection closed by invalid user qffpr 34.140.148.49 port 52188 [preauth]
...
show less
2026-09-02T03:34:05.432535+00:00 pega sshd-session[69990]: pam_unix(sshd:auth): authentication failu ...
show more2026-09-02T03:34:05.432535+00:00 pega sshd-session[69990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.140.148.49
2026-09-02T03:34:07.441317+00:00 pega sshd-session[69990]: Failed password for invalid user admin from 34.140.148.49 port 56066 ssh2
2026-09-02T03:34:07.713549+00:00 pega sshd-session[69990]: Connection closed by invalid user admin 34.140.148.49 port 56066 [preauth]
...
show less
2026-09-02T03:33:07.530711+00:00 matchpoint sshd[768064]: Invalid user admin from 34.140.148.49 port ...
show more2026-09-02T03:33:07.530711+00:00 matchpoint sshd[768064]: Invalid user admin from 34.140.148.49 port 33204
2026-09-02T03:33:07.563475+00:00 matchpoint sshd[768064]: Connection closed by invalid user admin 34.140.148.49 port 33204 [preauth]
2026-09-02T03:33:09.161388+00:00 matchpoint sshd[768034]: Connection closed by 34.140.148.49 port 33198 [preauth]
...
show less
SSH Brute force: 8 attempts were recorded from 34.140.148.49
2026-09-02T05:10:14+02:00 Invalid user ...
show moreSSH Brute force: 8 attempts were recorded from 34.140.148.49
2026-09-02T05:10:14+02:00 Invalid user admin from 34.140.148.49 port 42290
2026-09-02T04:18:00+02:00 Invalid user rtnlp from 34.140.148.49 port 45118
2026-09-02T04:55:21+02:00 Invalid user admin from 34.140.148.49 port 6128
2026-09-02T04:15:11+02:00 Invalid user admin from 34.140.148.49 port 64324
2026-09-02T04:42:35+02:00 Invalid user eqyhx from 34.140.148.49 port 10008
2026-09-02T04:37:33+02:00 Invalid user suhui from 34.140.148.49 port 10170
2026-09-02T04:10:49+02:00 Invalid user admin from 34.140.148.49 port 32852
2026-09-02T04:08:27+02:00 Invalid user admin from 34.140.148.49 port 27724
show less
2026-09-02T05:17:15.977239+02:00 ubuntu-server sshd[1692236]: Invalid user admin from 34.140.148.49 ...
show more2026-09-02T05:17:15.977239+02:00 ubuntu-server sshd[1692236]: Invalid user admin from 34.140.148.49 port 8710
...
show less
Honeypot hit: Brute-force attack detected on 22/SSH
• Credentials: admin:admin, admin:password
• Num ...
show moreHoneypot hit: Brute-force attack detected on 22/SSH
• Credentials: admin:admin, admin:password
• Number of login attempts: 2
• Client: SSH-2.0-Fingerprintx-SSH2
show less
Fail2Ban SSH brute-force ban on bebricow.hostes.io. jail=sshd; source=fail2ban; no raw log lines inc ...
show moreFail2Ban SSH brute-force ban on bebricow.hostes.io. jail=sshd; source=fail2ban; no raw log lines included.
show less
Brute-Force
SSH
Showing 1 to
15
of 41 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩