This IP address has been reported a total of
65
times from
65 distinct
sources.
138.68.29.11 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 17
reports;
United States of America
with 11
reports;
United Kingdom of Great Britain and Northern Ireland
with 5
reports.
The most common categories in these recent reports were:
Brute-Force
59
times;
SSH
58
times;
Port Scan
5
times;
Hacking
2
times;
Web App Attack
1
time.
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.
Knock-Knock honeypot brute-force: SSH (8 total hits)
Brute-Force
SSH
Anonymous
2026-10-17T23:58:39.473638+00:00 de-fra2-dns3 sshd[1657015]: Invalid user john from 138.68.29.11 por ...
show more2026-10-17T23:58:39.473638+00:00 de-fra2-dns3 sshd[1657015]: Invalid user john from 138.68.29.11 port 54610
2026-10-18T00:09:20.313947+00:00 de-fra2-dns3 sshd[1657203]: Invalid user david from 138.68.29.11 port 59244
2026-10-18T00:12:06.784518+00:00 de-fra2-dns3 sshd[1657492]: Invalid user richard from 138.68.29.11 port 41050
...
show less
Automated honeypot observation: SSH brute-force / credential-stuffing. Failed logins: 5, successful: ...
show moreAutomated honeypot observation: SSH brute-force / credential-stuffing. Failed logins: 5, successful: 0, commands: 0, file transfers: 0. Seen on 1 sensor(s) (us1) over 2026-10-17..2026-10-18. Reported by an SSH honeypot network; no production service involved.
show less
Brute-Force
SSH
Anonymous
SSH brute force attempt. User: richard, Pass: [REDACTED]
2026-10-18T01:56:37.283098+02:00 03-at sshd[1633600]: Invalid user james from 138.68.29.11 port 3386 ...
show more2026-10-18T01:56:37.283098+02:00 03-at sshd[1633600]: Invalid user james from 138.68.29.11 port 33862
2026-10-18T01:59:07.644541+02:00 03-at sshd[1633862]: Invalid user john from 138.68.29.11 port 57524
2026-10-18T02:01:49.270346+02:00 03-at sshd[1634726]: Invalid user robert from 138.68.29.11 port 36838
2026-10-18T02:04:32.827925+02:00 03-at sshd[1634974]: Invalid user michael from 138.68.29.11 port 40972
2026-10-18T02:07:11.721690+02:00 03-at sshd[1635338]: Invalid user william from 138.68.29.11 port 47994
...
show less
2026-10-18T01:58:19.023383+02:00 Linux12 sshd-session[206001]: Failed password for invalid user john ...
show more2026-10-18T01:58:19.023383+02:00 Linux12 sshd-session[206001]: Failed password for invalid user john from 138.68.29.11 port 45250 ssh2
2026-10-18T02:00:51.142346+02:00 Linux12 sshd-session[214395]: Invalid user robert from 138.68.29.11 port 41584
2026-10-18T02:00:51.317343+02:00 Linux12 sshd-session[214395]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.29.11
2026-10-18T02:00:53.499365+02:00 Linux12 sshd-session[214395]: Failed password for invalid user robert from 138.68.29.11 port 41584 ssh2
2026-10-18T02:03:35.909108+02:00 Linux12 sshd-session[222154]: Invalid user michael from 138.68.29.11 port 56282
2026-10-18T02:03:36.096589+02:00 Linux12 sshd-session[222154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.29.11
2026-10-18T02:03:37.780383+02:00 Linux12 sshd-session[222154]: Failed password for invalid user michael from 138.68.29.11 port 56282 ssh2
2026-10-18T02:06:16.875393+02:00 Linu
...
show less
2026-10-17T23:55:40.632702+00:00 theurer-dev sshd[32293]: Invalid user james from 138.68.29.11 port ...
show more2026-10-17T23:55:40.632702+00:00 theurer-dev sshd[32293]: Invalid user james from 138.68.29.11 port 38520
2026-10-17T23:58:12.794035+00:00 theurer-dev sshd[32342]: Invalid user john from 138.68.29.11 port 42738
2026-10-18T00:00:47.271478+00:00 theurer-dev sshd[32359]: Invalid user robert from 138.68.29.11 port 49292
2026-10-18T00:03:31.671950+00:00 theurer-dev sshd[32370]: Invalid user michael from 138.68.29.11 port 44540
2026-10-18T00:06:12.988645+00:00 theurer-dev sshd[32378]: Invalid user william from 138.68.29.11 port 42686
show less
SSH scanning: repeated logins with invalid usernames against a key-only server. Reported by fail2ban ...
show moreSSH scanning: repeated logins with invalid usernames against a key-only server. Reported by fail2ban.
show less
