This IP address has been reported a total of
113
times from
82 distinct
sources.
203.200.74.20 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.
Aug 29 08:12:21 mags sshd-session[3168659]: Invalid user user2 from 203.200.74.20 port 39592
Aug 29 ...
show moreAug 29 08:12:21 mags sshd-session[3168659]: Invalid user user2 from 203.200.74.20 port 39592
Aug 29 08:14:59 mags sshd-session[3168689]: Invalid user shiva from 203.200.74.20 port 34024
Aug 29 08:24:20 mags sshd-session[3170542]: Invalid user parth from 203.200.74.20 port 13458
Aug 29 08:26:58 mags sshd-session[3171334]: Invalid user health from 203.200.74.20 port 42128
Aug 29 08:29:40 mags sshd-session[3171387]: Invalid user rd from 203.200.74.20 port 10708
Aug 29 08:30:58 mags sshd-session[3172246]: Invalid user christophe from 203.200.74.20 port 53914
Aug 29 08:32:15 mags sshd-session[3172290]: Invalid user bench from 203.200.74.20 port 64268
...
show less
2026-08-29T06:13:03.915758+08:00 nekoaru-shanghai-1 sshd-session[1047898]: Invalid user user2 from 2 ...
show more2026-08-29T06:13:03.915758+08:00 nekoaru-shanghai-1 sshd-session[1047898]: Invalid user user2 from 203.200.74.20 port 20572
2026-08-29T06:13:03.918287+08:00 nekoaru-shanghai-1 sshd-session[1047898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.200.74.20
2026-08-29T06:13:05.819626+08:00 nekoaru-shanghai-1 sshd-session[1047898]: Failed password for invalid user user2 from 203.200.74.20 port 20572 ssh2
...
show less
2026-08-28T20:56:22.015584Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:4871 ...
show more2026-08-28T20:56:22.015584Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:48710 (158.69.22.11:2222) [session: 244cba3955b4]
2026-08-28T20:57:37.053616Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:1700 (158.69.22.11:2222) [session: 9e43976e8690]
...
show less
2026-08-28T21:47:56.427887+01:00 srv02 sshd-session[1809303]: pam_unix(sshd:auth): authentication fa ...
show more2026-08-28T21:47:56.427887+01:00 srv02 sshd-session[1809303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.200.74.20
2026-08-28T21:47:58.510306+01:00 srv02 sshd-session[1809303]: Failed password for invalid user qwert from 203.200.74.20 port 27234 ssh2
2026-08-28T21:49:15.916513+01:00 srv02 sshd-session[1810014]: Invalid user wso2 from 203.200.74.20 port 17648
2026-08-28T21:49:15.920301+01:00 srv02 sshd-session[1810014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.200.74.20
2026-08-28T21:49:17.831317+01:00 srv02 sshd-session[1810014]: Failed password for invalid user wso2 from 203.200.74.20 port 17648 ssh2
...
show less
2026-08-28T21:20:41.923333+01:00 srv02 sshd-session[1792727]: Failed password for invalid user ftpus ...
show more2026-08-28T21:20:41.923333+01:00 srv02 sshd-session[1792727]: Failed password for invalid user ftpuser from 203.200.74.20 port 7360 ssh2
2026-08-28T21:21:58.373649+01:00 srv02 sshd-session[1793446]: Invalid user luka from 203.200.74.20 port 41964
2026-08-28T21:21:58.377447+01:00 srv02 sshd-session[1793446]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.200.74.20
2026-08-28T21:22:00.000586+01:00 srv02 sshd-session[1793446]: Failed password for invalid user luka from 203.200.74.20 port 41964 ssh2
2026-08-28T21:23:16.348985+01:00 srv02 sshd-session[1794152]: Invalid user dante from 203.200.74.20 port 39972
...
show less
2026-08-28T19:53:38.675422Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:1444 ...
show more2026-08-28T19:53:38.675422Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:14442 (158.69.22.11:2222) [session: f72fef34f204]
2026-08-28T19:55:24.767657Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 203.200.74.20:64002 (158.69.22.11:2222) [session: 95567053e42a]
...
show less
2026-08-28T21:49:59.141797+02:00 r2d2 sshd-session[96027]: Invalid user king from 203.200.74.20 port ...
show more2026-08-28T21:49:59.141797+02:00 r2d2 sshd-session[96027]: Invalid user king from 203.200.74.20 port 3614
...
show less
Aug 28 18:42:37 server sshd[418880]: Invalid user ca from 203.200.74.20 port 34838
Aug 28 18:45:22 s ...
show moreAug 28 18:42:37 server sshd[418880]: Invalid user ca from 203.200.74.20 port 34838
Aug 28 18:45:22 server sshd[418904]: Invalid user test from 203.200.74.20 port 2770
Aug 28 18:46:44 server sshd[418924]: Invalid user deployer from 203.200.74.20 port 28274
...
show less
Automated SSH brute-force report by Fail2Ban on Node 2 - NXP Game-Server (134.255.219.74) (NXP Infra ...
show moreAutomated SSH brute-force report by Fail2Ban on Node 2 - NXP Game-Server (134.255.219.74) (NXP Infrastructure). The IP attempted unauthorized SSH access multiple times within a short timeframe.
show less
2026-08-28T16:51:53.610182+00:00 debian-4gb-nbg1-1 sshd-session[1383224]: Invalid user sasaki from 2 ...
show more2026-08-28T16:51:53.610182+00:00 debian-4gb-nbg1-1 sshd-session[1383224]: Invalid user sasaki from 203.200.74.20 port 45468
2026-08-28T16:54:26.792322+00:00 debian-4gb-nbg1-1 sshd-session[1383232]: Invalid user sachi from 203.200.74.20 port 31082
...
show less
Brute-Force
SSH
Showing 1 to
15
of 113 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩