This IP address has been reported a total of
1,146
times from
278 distinct
sources.
122.137.242.20 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.
Aug 18 16:06:51 mail sshd[559020]: Failed password for root from 122.137.242.20 port 3156 ssh2
Aug 1 ...
show moreAug 18 16:06:51 mail sshd[559020]: Failed password for root from 122.137.242.20 port 3156 ssh2
Aug 18 16:06:54 mail sshd[559023]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 18 16:06:56 mail sshd[559023]: Failed password for root from 122.137.242.20 port 3157 ssh2
Aug 18 16:06:59 mail sshd[559026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 18 16:07:01 mail sshd[559026]: Failed password for root from 122.137.242.20 port 3158 ssh2
...
show less
Report 1816617 with IP 275021 for SSH brute-force attack by source 2858842 via ssh-honeypot/0.2.0+ht ...
show moreReport 1816617 with IP 275021 for SSH brute-force attack by source 2858842 via ssh-honeypot/0.2.0+http
show less
2025-08-18T05:28:41.930049+02:00 deb sshd[824045]: Failed password for root from 122.137.242.20 port ...
show more2025-08-18T05:28:41.930049+02:00 deb sshd[824045]: Failed password for root from 122.137.242.20 port 3012 ssh2
2025-08-18T05:28:45.318171+02:00 deb sshd[824048]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
2025-08-18T05:28:47.207100+02:00 deb sshd[824048]: Failed password for root from 122.137.242.20 port 3013 ssh2
2025-08-18T05:28:50.491405+02:00 deb sshd[824050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
2025-08-18T05:28:52.400410+02:00 deb sshd[824050]: Failed password for root from 122.137.242.20 port 3014 ssh2
...
show less
(sshd) Failed SSH login from 122.137.242.20 (CN/China/20.242.137.122.adsl-pool.jlccptt.net.cn): 5 in ...
show more(sshd) Failed SSH login from 122.137.242.20 (CN/China/20.242.137.122.adsl-pool.jlccptt.net.cn): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Aug 17 21:56:06 17123 sshd[9887]: Did not receive identification string from 122.137.242.20 port 3370
Aug 17 21:56:08 17123 sshd[9888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 17 21:56:11 17123 sshd[9888]: Failed password for root from 122.137.242.20 port 3371 ssh2
Aug 17 21:56:15 17123 sshd[9893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 17 21:56:17 17123 sshd[9893]: Failed password for root from 122.137.242.20 port 3372 ssh2
show less
ThreatBook Intelligence: Zombie,Scanner more details on https://threatbook.io/ip/122.137.242.20
2025 ...
show moreThreatBook Intelligence: Zombie,Scanner more details on https://threatbook.io/ip/122.137.242.20
2025-08-17 17:37:12 ["uname -s -m"]
show less
(sshd) Failed SSH login from 122.137.242.20 (CN/China/20.242.137.122.adsl-pool.jlccptt.net.cn): 5 in ...
show more(sshd) Failed SSH login from 122.137.242.20 (CN/China/20.242.137.122.adsl-pool.jlccptt.net.cn): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Aug 17 16:35:05 15181 sshd[18790]: Did not receive identification string from 122.137.242.20 port 2968
Aug 17 16:35:07 15181 sshd[18791]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 17 16:35:10 15181 sshd[18791]: Failed password for root from 122.137.242.20 port 2969 ssh2
Aug 17 16:35:16 15181 sshd[18793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.137.242.20 user=root
Aug 17 16:35:17 15181 sshd[18793]: Failed password for root from 122.137.242.20 port 2970 ssh2
show less
Brute-Force
SSH
Showing 1 to
15
of 1146 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩