This IP address has been reported a total of
874
times from
155 distinct
sources.
104.243.37.202 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.
May 30 07:50:22 netllama sshd-session[1958017]: User root from 104.243.37.202 not allowed because no ...
show moreMay 30 07:50:22 netllama sshd-session[1958017]: User root from 104.243.37.202 not allowed because not listed in AllowUsers
May 30 07:50:22 netllama sshd-session[1958017]: error: maximum authentication attempts exceeded for invalid user root from 104.243.37.202 port 6306 ssh2 [preauth]
...
show less
May 29 23:44:52 uptime-kuma sshd[841821]: Disconnected from authenticating user root 104.243.37.202 ...
show moreMay 29 23:44:52 uptime-kuma sshd[841821]: Disconnected from authenticating user root 104.243.37.202 port 23478 [preauth]
...
show less
This IP address carried out 20 port scanning attempts on 29-05-2026. For more information or to repo ...
show moreThis IP address carried out 20 port scanning attempts on 29-05-2026. For more information or to report interesting / incorrect findings, give me a shoutout @parthmaniar on Twitter.
show less
May 30 00:27:41 ***** sshd[2376728]: User root from 104.243.37.202 not allowed because not listed in ...
show moreMay 30 00:27:41 ***** sshd[2376728]: User root from 104.243.37.202 not allowed because not listed in AllowUsers
show less
May 28 18:51:10 digamma sshd[296761]: User root from 104.243.37.202 not allowed because none of user ...
show moreMay 28 18:51:10 digamma sshd[296761]: User root from 104.243.37.202 not allowed because none of user's groups are listed in AllowGroups
May 29 12:41:21 digamma sshd[328502]: User root from 104.243.37.202 not allowed because none of user's groups are listed in AllowGroups
May 29 14:57:15 digamma sshd[331807]: User root from 104.243.37.202 not allowed because none of user's groups are listed in AllowGroups
...
show less
2026-05-30T04:39:40.103250+09:00 no3 sshd[2079484]: Disconnected from authenticating user root 104.2 ...
show more2026-05-30T04:39:40.103250+09:00 no3 sshd[2079484]: Disconnected from authenticating user root 104.243.37.202 port 14858 [preauth]
...
show less
2026-05-30T03:17:46.686208+08:00 vps-ebd448c1 sshd-session[2476900]: Failed publickey for root from ...
show more2026-05-30T03:17:46.686208+08:00 vps-ebd448c1 sshd-session[2476900]: Failed publickey for root from 104.243.37.202 port 40720 ssh2: RSA SHA256:TlrsZgRlMAxRYPHDXi6fc9nR7/IzQGyxiEM368q4J08
2026-05-30T03:17:46.924602+08:00 vps-ebd448c1 sshd-session[2476900]: Failed publickey for root from 104.243.37.202 port 40720 ssh2: ED25519 SHA256:qgIPxnS9n2g30boC+5E9bI0ok/r3LaXB6YpRbyU+T2k
2026-05-30T03:17:47.163262+08:00 vps-ebd448c1 sshd-session[2476900]: Failed publickey for root from 104.243.37.202 port 40720 ssh2: RSA SHA256:C2paK1SHirM2vb0mfePLkNjZWRk+4aL22SXmnK7hIyc
show less
Suricata Detected 2 attacks from 104.243.37.202.; ET SCAN LibSSH Based Frequent SSH Connections Like ...
show moreSuricata Detected 2 attacks from 104.243.37.202.; ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack; IP: 104.243.37.202; Ports: 57170; Direction: to_server; Trigger: SCAN; Category: Attempted Administrator Privilege Gain; Severity: 1
show less