This IP address has been reported a total of
187
times from
117 distinct
sources.
121.122.65.136 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 121.122.65.136 (MY/Malaysia/-): 5 in the last 3600 secs; Ports: *; Dire ...
show more(sshd) Failed SSH login from 121.122.65.136 (MY/Malaysia/-): 5 in the last 3600 secs; Ports: *; Direction: 1; Trigger: LF_SSHD; Logs: Apr 23 21:37:30 14669 sshd[6448]: Invalid user postgres from 121.122.65.136 port 7394
Apr 23 21:37:32 14669 sshd[6448]: Failed password for invalid user postgres from 121.122.65.136 port 7394 ssh2
Apr 23 21:55:28 14669 sshd[7877]: Invalid user postgres from 121.122.65.136 port 21103
Apr 23 21:55:30 14669 sshd[7877]: Failed password for invalid user postgres from 121.122.65.136 port 21103 ssh2
Apr 23 21:56:32 14669 sshd[7949]: Invalid user postgres from 121.122.65.136 port 47531
show less
Apr 24 04:55:38 web sshd[11712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 ...
show moreApr 24 04:55:38 web sshd[11712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.122.65.136
Apr 24 04:55:40 web sshd[11712]: Failed password for invalid user postgres from 121.122.65.136 port 24343 ssh2
Apr 24 04:56:42 web sshd[11884]: Invalid user postgres from 121.122.65.136 port 27732
...
show less
2026-04-23T22:46:52.635009-04:00 Host-KEWR-E sshd[73127]: Connection closed by 121.122.65.136 port 3 ...
show more2026-04-23T22:46:52.635009-04:00 Host-KEWR-E sshd[73127]: Connection closed by 121.122.65.136 port 38077 [preauth]
...
show less
2026-04-24T03:05:45.837926+01:00 ns3124905 sshd-session[3672878]: pam_unix(sshd:auth): authenticatio ...
show more2026-04-24T03:05:45.837926+01:00 ns3124905 sshd-session[3672878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.122.65.136
2026-04-24T03:05:47.661015+01:00 ns3124905 sshd-session[3672878]: Failed password for invalid user postgres from 121.122.65.136 port 33052 ssh2
2026-04-24T03:06:48.599904+01:00 ns3124905 sshd-session[3673067]: Invalid user mqm from 121.122.65.136 port 6762
...
show less
2026-04-24T02:26:00.182467+02:00 Pi.sebi.org sshd-session[112282]: Invalid user server from 121.122. ...
show more2026-04-24T02:26:00.182467+02:00 Pi.sebi.org sshd-session[112282]: Invalid user server from 121.122.65.136 port 57224
2026-04-24T02:26:59.706175+02:00 Pi.sebi.org sshd-session[112291]: Invalid user gitea from 121.122.65.136 port 53566
2026-04-24T02:28:24.528668+02:00 Pi.sebi.org sshd-session[112305]: Invalid user ts1 from 121.122.65.136 port 47666
2026-04-24T02:29:22.959561+02:00 Pi.sebi.org sshd-session[112313]: Invalid user teamspeak from 121.122.65.136 port 40772
2026-04-24T02:33:12.374962+02:00 Pi.sebi.org sshd-session[112363]: Invalid user maha from 121.122.65.136 port 47417
show less
Brute-Force
SSH
Showing 1 to
15
of 187 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩