This IP address has been reported a total of
254
times from
170 distinct
sources.
2.134.15.12 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-06-04T02:17:39.371371+00:00 lan.updn.io sshd[737756]: Failed password for invalid user abc from ...
show more2026-06-04T02:17:39.371371+00:00 lan.updn.io sshd[737756]: Failed password for invalid user abc from 2.134.15.12 port 42470 ssh2
2026-06-04T02:24:41.720615+00:00 lan.updn.io sshd[765757]: Invalid user serv from 2.134.15.12 port 40250
2026-06-04T02:24:41.724714+00:00 lan.updn.io sshd[765757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.134.15.12
2026-06-04T02:24:43.639271+00:00 lan.updn.io sshd[765757]: Failed password for invalid user serv from 2.134.15.12 port 40250 ssh2
2026-06-04T02:27:10.661988+00:00 lan.updn.io sshd[775806]: Invalid user librenms from 2.134.15.12 port 57452
...
show less
Failed 10 attempts using usernames: alex, kibana, user, amalia, user123, frappe, nexus, marketing, c ...
show moreFailed 10 attempts using usernames: alex, kibana, user, amalia, user123, frappe, nexus, marketing, contact and test
show less
Jun 3 19:27:33 b146-27 sshd[357197]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eu ...
show moreJun 3 19:27:33 b146-27 sshd[357197]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.134.15.12
Jun 3 19:27:35 b146-27 sshd[357197]: Failed password for invalid user alex from 2.134.15.12 port 52094 ssh2
Jun 3 19:32:07 b146-27 sshd[357232]: Invalid user kibana from 2.134.15.12 port 38272
...
show less
2026-06-04T01:21:16.163994+02:00 axisverse sshd-session[1050371]: Invalid user debian from 2.134.15. ...
show more2026-06-04T01:21:16.163994+02:00 axisverse sshd-session[1050371]: Invalid user debian from 2.134.15.12 port 38934
2026-06-04T01:23:28.241160+02:00 axisverse sshd-session[1053947]: Invalid user jc from 2.134.15.12 port 60116
2026-06-04T01:25:33.332985+02:00 axisverse sshd-session[1057360]: Invalid user hamza from 2.134.15.12 port 48998
...
show less
SSH Brute Force (3 attempts). Evidence: sshd[42035]: Disconnected from authenticating user root 2.13 ...
show moreSSH Brute Force (3 attempts). Evidence: sshd[42035]: Disconnected from authenticating user root 2.134.15.12 port 42744 [preauth];sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.134.15.12 user=root
show less
2026-06-03T21:45:13.085753+00:00 de-fra2-srt1 sshd[816367]: Invalid user postgres from 2.134.15.12 p ...
show more2026-06-03T21:45:13.085753+00:00 de-fra2-srt1 sshd[816367]: Invalid user postgres from 2.134.15.12 port 33830
2026-06-03T21:56:40.387719+00:00 de-fra2-srt1 sshd[816654]: Invalid user botuser from 2.134.15.12 port 51332
2026-06-03T22:01:02.153275+00:00 de-fra2-srt1 sshd[816698]: Invalid user almalinux from 2.134.15.12 port 41594
...
show less
Jun 3 21:58:21 ubuntu-8gb-hel1-2 sshd[427030]: Invalid user botuser from 2.134.15.12 port 36350
Jun ...
show moreJun 3 21:58:21 ubuntu-8gb-hel1-2 sshd[427030]: Invalid user botuser from 2.134.15.12 port 36350
Jun 3 21:58:21 ubuntu-8gb-hel1-2 sshd[427030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.134.15.12
Jun 3 21:58:23 ubuntu-8gb-hel1-2 sshd[427030]: Failed password for invalid user botuser from 2.134.15.12 port 36350 ssh2
...
show less
2026-06-03T22:35:48.618426+02:00 axisverse sshd-session[778823]: Invalid user wow from 2.134.15.12 p ...
show more2026-06-03T22:35:48.618426+02:00 axisverse sshd-session[778823]: Invalid user wow from 2.134.15.12 port 42628
2026-06-03T22:38:07.599827+02:00 axisverse sshd-session[783237]: Invalid user braun from 2.134.15.12 port 40584
2026-06-03T22:40:09.215507+02:00 axisverse sshd-session[787050]: Invalid user yangj from 2.134.15.12 port 54232
...
show less
Brute-Force
SSH
Anonymous
Web App Attack
Showing 1 to
15
of 254 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩