This IP address has been reported a total of
227
times from
164 distinct
sources.
174.138.44.8 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 174.138.44.8 (US/United States/-): 5 in the last 3600 secs; Ports: *; D ...
show more(sshd) Failed SSH login from 174.138.44.8 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Jun 29 04:54:36 15520 sshd[3626]: Invalid user root2 from 174.138.44.8 port 60574
Jun 29 04:54:38 15520 sshd[3626]: Failed password for invalid user root2 from 174.138.44.8 port 60574 ssh2
Jun 29 05:06:49 15520 sshd[10523]: Invalid user server from 174.138.44.8 port 41728
Jun 29 05:06:50 15520 sshd[10523]: Failed password for invalid user server from 174.138.44.8 port 41728 ssh2
Jun 29 05:08:13 15520 sshd[11431]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8 user=root
show less
Jun 29 09:56:02 ice2 sshd[2213908]: Invalid user root2 from 174.138.44.8 port 58944
Jun 29 10:06:57 ...
show moreJun 29 09:56:02 ice2 sshd[2213908]: Invalid user root2 from 174.138.44.8 port 58944
Jun 29 10:06:57 ice2 sshd[2213970]: Invalid user server from 174.138.44.8 port 48572
...
show less
(sshd) Failed SSH login from 174.138.44.8 (US/United States/-): 5 in the last 3600 secs; Ports: *; D ...
show more(sshd) Failed SSH login from 174.138.44.8 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Jun 29 02:28:11 13979 sshd[4511]: Invalid user pgsql from 174.138.44.8 port 36946
Jun 29 02:28:13 13979 sshd[4511]: Failed password for invalid user pgsql from 174.138.44.8 port 36946 ssh2
Jun 29 02:40:21 13979 sshd[10889]: Invalid user greetings from 174.138.44.8 port 60784
Jun 29 02:40:23 13979 sshd[10889]: Failed password for invalid user greetings from 174.138.44.8 port 60784 ssh2
Jun 29 02:41:48 13979 sshd[11566]: Invalid user ss from 174.138.44.8 port 60866
show less
2026-06-29T08:56:53.989499+02:00 behemoth sshd[1056475]: Invalid user user1 from 174.138.44.8 port 5 ...
show more2026-06-29T08:56:53.989499+02:00 behemoth sshd[1056475]: Invalid user user1 from 174.138.44.8 port 55044
2026-06-29T08:56:53.993330+02:00 behemoth sshd[1056475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8
2026-06-29T08:56:56.058533+02:00 behemoth sshd[1056475]: Failed password for invalid user user1 from 174.138.44.8 port 55044 ssh2
...
show less
Jun 29 06:56:19 v4bgp sshd[1360278]: Invalid user user1 from 174.138.44.8 port 53812
Jun 29 06:56:19 ...
show moreJun 29 06:56:19 v4bgp sshd[1360278]: Invalid user user1 from 174.138.44.8 port 53812
Jun 29 06:56:19 v4bgp sshd[1360278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8
Jun 29 06:56:21 v4bgp sshd[1360278]: Failed password for invalid user user1 from 174.138.44.8 port 53812 ssh2
...
show less
[rede-arem1] (sshd) Failed SSH login from 174.138.44.8 (US/United States/-): 5 in the last 3600 secs ...
show more[rede-arem1] (sshd) Failed SSH login from 174.138.44.8 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Jun 29 03:12:39 sshd[7146]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8 user=[USERNAME]
Jun 29 03:12:40 sshd[7146]: Failed password for [USERNAME] from 174.138.44.8 port 52566 ssh2
Jun 29 03:15:01 sshd[7301]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8 user=[USERNAME]
Jun 29 03:15:03 sshd[7301]: Failed password for [USERNAME] from 174.138.44.8 port 53480 ssh2
Jun 29 03:16:49 sshd[7
show less
2026-06-28T23:14:55.997488-07:00 server.vexstria.pro sshd[3367291]: Failed password for root from 17 ...
show more2026-06-28T23:14:55.997488-07:00 server.vexstria.pro sshd[3367291]: Failed password for root from 174.138.44.8 port 37428 ssh2
2026-06-28T23:16:42.498878-07:00 server.vexstria.pro sshd[3413158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8 user=root
2026-06-28T23:16:43.905638-07:00 server.vexstria.pro sshd[3413158]: Failed password for root from 174.138.44.8 port 58110 ssh2
...
show less
2026-06-29T11:44:32.182773+05:30 tribunal sshd-session[1181549]: Failed password for root from 174.1 ...
show more2026-06-29T11:44:32.182773+05:30 tribunal sshd-session[1181549]: Failed password for root from 174.138.44.8 port 32988 ssh2
2026-06-29T11:46:18.381881+05:30 tribunal sshd-session[1181951]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.44.8 user=root
2026-06-29T11:46:20.976471+05:30 tribunal sshd-session[1181951]: Failed password for root from 174.138.44.8 port 53646 ssh2
...
show less
Report 2513294 with IP 3554987 for SSH brute-force attack by source 3555519 via ssh-honeypot/0.2.1+h ...
show moreReport 2513294 with IP 3554987 for SSH brute-force attack by source 3555519 via ssh-honeypot/0.2.1+http
show less
Brute-Force
SSH
Showing 1 to
15
of 227 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩