This IP address has been reported a total of
20
times from
16 distinct
sources.
178.13.66.220 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 6
reports;
Hong Kong
with 3
reports;
Poland
with 3
reports.
The most common categories in these recent reports were:
Brute-Force
13
times;
Web App Attack
8
times;
Hacking
5
times;
SSH
4
times;
Port Scan
3
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.
Web directory scan: 10 requests in 4h 18m (Last path: '/webapi/auth.cgi?account=muhely&api=SYNO.API. ...
show moreWeb directory scan: 10 requests in 4h 18m (Last path: '/webapi/auth.cgi?account=muhely&api=SYNO.API.Auth&format=sid&method=login&passwd=muhely&session=FileStation&version=6').
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:07:42.686573+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:07:42.686] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=178.13.66.220:57740 2026-10-04T21:07:44.272954+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:07:44.272] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=178.13.66.220:59022 2026-10-04T21:07:47.237810+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:07:47.237] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=178.13.66.220:59012 ...
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:22:42 isp sshd[3975707]: Failed password for root from 178.13.66.220 port 41796 ssh2
Oct ...
show moreOct 4 20:22:42 isp sshd[3975707]: Failed password for root from 178.13.66.220 port 41796 ssh2
Oct 4 20:26:21 isp sshd[3978620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.13.66.220 user=root
Oct 4 20:26:24 isp sshd[3978620]: Failed password for root from 178.13.66.220 port 50710 ssh2
...
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
User [luke] from [178.13.66.220] failed to sign in to [DSM] via [password] due to authorization fail ...
show moreUser [luke] from [178.13.66.220] failed to sign in to [DSM] via [password] due to authorization failure.
show less
Brute-Force
Anonymous
Web directory scan: 10 requests in 23h 58m (Last path: '/webapi/auth.cgi?account=luke&api=SYNO.API.A ...
show moreWeb directory scan: 10 requests in 23h 58m (Last path: '/webapi/auth.cgi?account=luke&api=SYNO.API.Auth&format=sid&method=login&passwd=luke&session=FileStation&version=6').
show less
Failed logins to a Synology NAS: 6 attempts via DSM, 2026-10-01 20:25 to 2026-10-02 08:56 UTC. Usern ...
show moreFailed logins to a Synology NAS: 6 attempts via DSM, 2026-10-01 20:25 to 2026-10-02 08:56 UTC. Usernames tried: administrator, sales (+4 others).
show less
