This IP address has been reported a total of
32
times from
24 distinct
sources.
134.209.228.124 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
2026-03-02T06:02:54.037091shield sshd\[14851\]: Invalid user oracle from 134.209.228.124 port 42930
...
show more2026-03-02T06:02:54.037091shield sshd\[14851\]: Invalid user oracle from 134.209.228.124 port 42930
2026-03-02T06:02:54.204893shield sshd\[14851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
2026-03-02T06:02:55.997938shield sshd\[14851\]: Failed password for invalid user oracle from 134.209.228.124 port 42930 ssh2
2026-03-02T06:03:21.199929shield sshd\[14953\]: Invalid user oracle from 134.209.228.124 port 37290
2026-03-02T06:03:21.350344shield sshd\[14953\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
show less
2026-03-02T00:59:43.875978 mono sshd[1121540]: Invalid user postgres from 134.209.228.124 port 37232 ...
show more2026-03-02T00:59:43.875978 mono sshd[1121540]: Invalid user postgres from 134.209.228.124 port 37232
2026-03-02T01:00:13.963126 mono sshd[1121546]: Invalid user postgres from 134.209.228.124 port 33730
2026-03-02T01:00:43.597631 mono sshd[1121551]: Invalid user postgres from 134.209.228.124 port 46026
2026-03-02T01:01:13.828461 mono sshd[1121561]: Invalid user postgres from 134.209.228.124 port 58246
2026-03-02T01:01:44.221024 mono sshd[1121569]: Invalid user postgres from 134.209.228.124 port 43382
...
show less
2026-03-02T05:53:42.944444+00:00 panel sshd[594003]: Failed password for invalid user postgres from ...
show more2026-03-02T05:53:42.944444+00:00 panel sshd[594003]: Failed password for invalid user postgres from 134.209.228.124 port 47524 ssh2
2026-03-02T05:54:10.262883+00:00 panel sshd[601937]: Invalid user postgres from 134.209.228.124 port 45818
2026-03-02T05:54:10.390019+00:00 panel sshd[601937]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
2026-03-02T05:54:12.581232+00:00 panel sshd[601937]: Failed password for invalid user postgres from 134.209.228.124 port 45818 ssh2
2026-03-02T05:54:40.332680+00:00 panel sshd[608386]: Invalid user postgres from 134.209.228.124 port 53862
...
show less
2026-03-02T05:52:12.508062shield sshd\[12844\]: Invalid user postgres from 134.209.228.124 port 5659 ...
show more2026-03-02T05:52:12.508062shield sshd\[12844\]: Invalid user postgres from 134.209.228.124 port 56590
2026-03-02T05:52:12.613644shield sshd\[12844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
2026-03-02T05:52:14.607781shield sshd\[12844\]: Failed password for invalid user postgres from 134.209.228.124 port 56590 ssh2
2026-03-02T05:52:43.727221shield sshd\[12902\]: Invalid user postgres from 134.209.228.124 port 48046
2026-03-02T05:52:43.900104shield sshd\[12902\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
show less
2026-03-02T00:48:31.883393-05:00 proxy sshd-session[494254]: Invalid user postgres from 134.209.228. ...
show more2026-03-02T00:48:31.883393-05:00 proxy sshd-session[494254]: Invalid user postgres from 134.209.228.124 port 43774
...
show less
2026-03-02T05:41:32.737133shield sshd\[11304\]: Invalid user pul from 134.209.228.124 port 38668
202 ...
show more2026-03-02T05:41:32.737133shield sshd\[11304\]: Invalid user pul from 134.209.228.124 port 38668
2026-03-02T05:41:32.821832shield sshd\[11304\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
2026-03-02T05:41:34.951571shield sshd\[11304\]: Failed password for invalid user pul from 134.209.228.124 port 38668 ssh2
2026-03-02T05:42:02.898648shield sshd\[11368\]: Invalid user yuanwd from 134.209.228.124 port 38884
2026-03-02T05:42:02.982385shield sshd\[11368\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.228.124
show less
2026-03-02T00:30:31.397489 mono sshd[1120962]: Invalid user test1 from 134.209.228.124 port 44604
20 ...
show more2026-03-02T00:30:31.397489 mono sshd[1120962]: Invalid user test1 from 134.209.228.124 port 44604
2026-03-02T00:31:15.164960 mono sshd[1120969]: Invalid user test2 from 134.209.228.124 port 56018
2026-03-02T00:31:51.703232 mono sshd[1120971]: Invalid user test3 from 134.209.228.124 port 44742
2026-03-02T00:36:48.282333 mono sshd[1121025]: Invalid user postgres from 134.209.228.124 port 55502
2026-03-02T00:37:21.858446 mono sshd[1121033]: Invalid user oracle from 134.209.228.124 port 51218
...
show less
Mar 2 06:30:32 saltoalvacio sshd[793500]: Invalid user test1 from 134.209.228.124 port 45406
Mar 2 ...
show moreMar 2 06:30:32 saltoalvacio sshd[793500]: Invalid user test1 from 134.209.228.124 port 45406
Mar 2 06:31:15 saltoalvacio sshd[793508]: Invalid user test2 from 134.209.228.124 port 50778
Mar 2 06:31:52 saltoalvacio sshd[793514]: Invalid user test3 from 134.209.228.124 port 59662
Mar 2 06:36:49 saltoalvacio sshd[793614]: Invalid user postgres from 134.209.228.124 port 49260
Mar 2 06:37:22 saltoalvacio sshd[793622]: Invalid user oracle from 134.209.228.124 port 35584
...
show less
Mar 2 07:30:59 pkdns2 sshd\[8330\]: Invalid user test1 from 134.209.228.124Mar 2 07:31:01 pkdns2 s ...
show moreMar 2 07:30:59 pkdns2 sshd\[8330\]: Invalid user test1 from 134.209.228.124Mar 2 07:31:01 pkdns2 sshd\[8330\]: Failed password for invalid user test1 from 134.209.228.124 port 38152 ssh2Mar 2 07:31:36 pkdns2 sshd\[8357\]: Invalid user test2 from 134.209.228.124Mar 2 07:31:38 pkdns2 sshd\[8357\]: Failed password for invalid user test2 from 134.209.228.124 port 53078 ssh2Mar 2 07:32:12 pkdns2 sshd\[8384\]: Invalid user test3 from 134.209.228.124Mar 2 07:32:14 pkdns2 sshd\[8384\]: Failed password for invalid user test3 from 134.209.228.124 port 36682 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 32 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩