This IP address has been reported a total of
7,534
times from
1,303 distinct
sources.
134.112.56.47 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.
(sshd) Failed SSH login from 134.112.56.47 (PL/Poland/-): 5 in the last 3600 secs; Ports: *; Directi ...
show more(sshd) Failed SSH login from 134.112.56.47 (PL/Poland/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Dec 30 23:06:39 15609 sshd[16695]: Invalid user vh from 134.112.56.47 port 55702
Dec 30 23:06:40 15609 sshd[16695]: Failed password for invalid user vh from 134.112.56.47 port 55702 ssh2
Dec 30 23:08:01 15609 sshd[16845]: Invalid user ubuntu from 134.112.56.47 port 46126
Dec 30 23:08:02 15609 sshd[16845]: Failed password for invalid user ubuntu from 134.112.56.47 port 46126 ssh2
Dec 30 23:09:55 15609 sshd[17138]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.112.56.47 user=root
show less
Brute-Force
SSH
Anonymous
2025-12-31T05:03:06.379171+00:00 rs2 sshd[1629536]: Invalid user vh from 134.112.56.47 port 45088
20 ...
show more2025-12-31T05:03:06.379171+00:00 rs2 sshd[1629536]: Invalid user vh from 134.112.56.47 port 45088
2025-12-31T05:07:38.630536+00:00 rs2 sshd[1629662]: Invalid user ubuntu from 134.112.56.47 port 45726
2025-12-31T05:10:15.550541+00:00 rs2 sshd[1629719]: Invalid user lijy from 134.112.56.47 port 34142
...
show less
Brute-Force
SSH
Anonymous
Dec 31 00:07:09 wp sshd[1513071]: Invalid user vh from 134.112.56.47 port 45868
Dec 31 00:07:11 wp s ...
show moreDec 31 00:07:09 wp sshd[1513071]: Invalid user vh from 134.112.56.47 port 45868
Dec 31 00:07:11 wp sshd[1513071]: Failed password for invalid user vh from 134.112.56.47 port 45868 ssh2
Dec 31 00:08:03 wp sshd[1513251]: Invalid user ubuntu from 134.112.56.47 port 46968
...
show less
Dec 31 05:06:43 v4bgp sshd[126887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid ...
show moreDec 31 05:06:43 v4bgp sshd[126887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.112.56.47
Dec 31 05:06:45 v4bgp sshd[126887]: Failed password for invalid user vh from 134.112.56.47 port 46946 ssh2
Dec 31 05:08:01 v4bgp sshd[126910]: Invalid user ubuntu from 134.112.56.47 port 44158
...
show less
(sshd) Failed SSH login from 134.112.56.47 (PL/Poland/-): 5 in the last 3600 secs; Ports: *; Directi ...
show more(sshd) Failed SSH login from 134.112.56.47 (PL/Poland/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Dec 30 22:24:53 14123 sshd[22206]: Invalid user toro from 134.112.56.47 port 54616
Dec 30 22:24:55 14123 sshd[22206]: Failed password for invalid user toro from 134.112.56.47 port 54616 ssh2
Dec 30 22:28:08 14123 sshd[22506]: Invalid user informix from 134.112.56.47 port 34630
Dec 30 22:28:11 14123 sshd[22506]: Failed password for invalid user informix from 134.112.56.47 port 34630 ssh2
Dec 30 22:32:20 14123 sshd[22833]: Invalid user db from 134.112.56.47 port 55190
show less
👿 134.112.56.47 has been involved in malicious and brute-force activity. Reported by umarmohammad.xy ...
show more👿 134.112.56.47 has been involved in malicious and brute-force activity. Reported by umarmohammad.xyz
show less
SSH brute force attack detected by fail2ban - attempted unauthorized access
Brute-Force
SSH
Anonymous
2025-12-31T02:00:13.932631+00:00 gaming1 sshd-session[1665219]: Invalid user ahmad from 134.112.56.4 ...
show more2025-12-31T02:00:13.932631+00:00 gaming1 sshd-session[1665219]: Invalid user ahmad from 134.112.56.47 port 38102
2025-12-31T02:02:08.049398+00:00 gaming1 sshd-session[1665572]: Invalid user ec2-user from 134.112.56.47 port 55156
2025-12-31T02:03:12.287971+00:00 gaming1 sshd-session[1665745]: Invalid user oracle from 134.112.56.47 port 49584
2025-12-31T02:05:22.737260+00:00 gaming1 sshd-session[1666135]: Invalid user logan from 134.112.56.47 port 42774
2025-12-31T02:07:16.322462+00:00 gaming1 sshd-session[1666479]: Invalid user sun from 134.112.56.47 port 44358
...
show less
Brute-Force
SSH
Anonymous
2025-12-31T01:23:58.045816+00:00 de-fra2-mirror1 sshd[2059354]: Invalid user admin from 134.112.56.4 ...
show more2025-12-31T01:23:58.045816+00:00 de-fra2-mirror1 sshd[2059354]: Invalid user admin from 134.112.56.47 port 38770
2025-12-31T01:36:39.605222+00:00 de-fra2-mirror1 sshd[2059901]: Invalid user dspace from 134.112.56.47 port 47950
2025-12-31T01:47:16.348295+00:00 de-fra2-mirror1 sshd[2059947]: Invalid user dev from 134.112.56.47 port 34152
...
show less
Dec 31 00:06:16 vmi1756752 sshd[1282811]: Failed password for invalid user justin from 134.112.56.47 ...
show moreDec 31 00:06:16 vmi1756752 sshd[1282811]: Failed password for invalid user justin from 134.112.56.47 port 55156 ssh2
Dec 31 00:10:41 vmi1756752 sshd[1284040]: Invalid user boost from 134.112.56.47 port 56600
Dec 31 00:10:41 vmi1756752 sshd[1284040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.112.56.47
Dec 31 00:10:42 vmi1756752 sshd[1284040]: Failed password for invalid user boost from 134.112.56.47 port 56600 ssh2
Dec 31 00:11:43 vmi1756752 sshd[1284257]: Invalid user cstrike from 134.112.56.47 port 59936
...
show less
Brute-Force
SSH
Showing 7426 to
7440
of 7534 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩