This IP address has been reported a total of
12
times from
12 distinct
sources.
122.116.204.52 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 4
reports;
Poland
with 2
reports;
Bangladesh
with 1
report.
The most common categories in these recent reports were:
Brute-Force
11
times;
SSH
4
times;
Web App Attack
3
times;
Hacking
2
times.
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.
Synology DSM web login brute-force: 2 failed sign-in attempt(s) between 16:57:18 and 20:06:19 CEST o ...
show moreSynology DSM web login brute-force: 2 failed sign-in attempt(s) between 16:57:18 and 20:06:19 CEST on 2026-10-06; part of distributed low-and-slow campaign (1000+ IPs).
show less
Brute-Force
Web App Attack
Anonymous
Web directory scan: 10 requests in 19h 34m (Last path: '/webapi/auth.cgi?account=okan&api=SYNO.API.A ...
show moreWeb directory scan: 10 requests in 19h 34m (Last path: '/webapi/auth.cgi?account=okan&api=SYNO.API.Auth&format=sid&method=login&passwd=q1w2e3&session=FileStation&version=6').
show less
Automated brute-force authentication attempt against Synology DSM management portal. Blocked by auto ...
show moreAutomated brute-force authentication attempt against Synology DSM management portal. Blocked by autoblock.
show less
Automated brute-force authentication attempt against Synology DSM management portal. Blocked by auto ...
show moreAutomated brute-force authentication attempt against Synology DSM management portal. Blocked by autoblock.
show less
SFTP Brute-Force login attempts or hacking probe detected against Pelican control panel. Evidence: 2 ...
show moreSFTP Brute-Force login attempts or hacking probe detected against Pelican control panel. Evidence: 2026-10-04T21:22:21.801919+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:22:21.801] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=122.116.204.52:53051 2026-10-04T21:22:28.516872+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:22:28.516] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=122.116.204.52:53689 2026-10-04T21:22:29.265073+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:22:29.265] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=122.116.204.52:53694 ...
show less
Suspicious brute-force activity was detected by MikroTik and the source IP was observed in the Brut_ ...
show moreSuspicious brute-force activity was detected by MikroTik and the source IP was observed in the Brut_knock stage tracking list.
show less
Oct 4 20:33:25 isp sshd[3984417]: Failed password for root from 122.116.204.52 port 52101 ssh2
Oct ...
show moreOct 4 20:33:25 isp sshd[3984417]: Failed password for root from 122.116.204.52 port 52101 ssh2
Oct 4 20:35:11 isp sshd[3985947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.116.204.52 user=root
Oct 4 20:35:13 isp sshd[3985947]: Failed password for root from 122.116.204.52 port 33527 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
12
of 12 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩
