This IP address has been reported a total of
84
times from
51 distinct
sources.
121.4.20.64 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-13T02:07:59.486950+03:00 nexus6 sshd[1449735]: Invalid user victor from 121.4.20.64 port 476 ...
show more2026-06-13T02:07:59.486950+03:00 nexus6 sshd[1449735]: Invalid user victor from 121.4.20.64 port 47628
...
show less
(sshd) Failed SSH login from 121.4.20.64 (CN/-/-): 5 in the last 3600 secs; Ports: *; Direction: ino ...
show more(sshd) Failed SSH login from 121.4.20.64 (CN/-/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 12 18:02:56 na-s3 sshd[3096690]: Invalid user ksiegowosc from 121.4.20.64 port 55682
Jun 12 18:38:05 na-s3 sshd[3512028]: Invalid user lch from 121.4.20.64 port 59672
Jun 12 18:39:15 na-s3 sshd[3525195]: Invalid user labs from 121.4.20.64 port 48388
Jun 12 18:41:06 na-s3 sshd[3547304]: Invalid user loguser from 121.4.20.64 port 38174
Jun 12 18:51:31 na-s3 sshd[3668841]: Invalid user vnc from 121.4.20.64 port 56786
show less
Automated SSH brute-force attack detected. The IP repeatedly attempted to authenticate to port 22 us ...
show moreAutomated SSH brute-force attack detected. The IP repeatedly attempted to authenticate to port 22 using multiple usernames and password guesses within a short timeframe.
show less
2026-06-11T02:03:57.299561+08:00 mg-us sshd[1607880]: Invalid user postgres from 121.4.20.64 port 56 ...
show more2026-06-11T02:03:57.299561+08:00 mg-us sshd[1607880]: Invalid user postgres from 121.4.20.64 port 56552
2026-06-11T02:03:57.304816+08:00 mg-us sshd[1607880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.4.20.64
2026-06-11T02:03:59.877543+08:00 mg-us sshd[1607880]: Failed password for invalid user postgres from 121.4.20.64 port 56552 ssh2
2026-06-11T02:05:36.407213+08:00 mg-us sshd[1607887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.4.20.64 user=root
2026-06-11T02:05:38.239678+08:00 mg-us sshd[1607887]: Failed password for root from 121.4.20.64 port 41464 ssh2
...
show less
2026-06-10T16:21:02.721445+00:00 mail sshd[35861]: Invalid user metal from 121.4.20.64 port 56424
.. ...
show more2026-06-10T16:21:02.721445+00:00 mail sshd[35861]: Invalid user metal from 121.4.20.64 port 56424
...
show less
2026-06-09T16:28:51.797438+02:00 jadzia sshd-session[735089]: Connection closed by 121.4.20.64 port ...
show more2026-06-09T16:28:51.797438+02:00 jadzia sshd-session[735089]: Connection closed by 121.4.20.64 port 44574 [preauth]
2026-06-09T16:36:08.882406+02:00 jadzia sshd-session[735625]: Connection closed by 121.4.20.64 port 49384 [preauth]
2026-06-09T16:41:23.544808+02:00 jadzia sshd-session[736044]: User root from 121.4.20.64 not allowed because not listed in AllowUsers
2026-06-09T16:41:24.417951+02:00 jadzia sshd-session[736044]: Disconnected from invalid user root 121.4.20.64 port 51006 [preauth]
2026-06-09T16:42:46.880174+02:00 jadzia sshd-session[736141]: Invalid user appuser from 121.4.20.64 port 34240
...
show less
Brute-Force
SSH
Showing 1 to
15
of 84 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown ๐ฉ