This IP address has been reported a total of
16
times from
13 distinct
sources.
80.15.82.243 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 5
reports;
Hong Kong
with 3
reports;
Poland
with 2
reports.
The most common categories in these recent reports were:
Brute-Force
11
times;
Web App Attack
7
times;
Hacking
4
times;
Port Scan
2
times;
SSH
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: 5 failed sign-in attempt(s) between 09:45:18 and 18:15:04 CEST o ...
show moreSynology DSM web login brute-force: 5 failed sign-in attempt(s) between 09:45:18 and 18:15:04 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 8h 45m (Last path: '/webapi/auth.cgi?account=server&api=SYNO.API. ...
show moreWeb directory scan: 10 requests in 8h 45m (Last path: '/webapi/auth.cgi?account=server&api=SYNO.API.Auth&format=sid&method=login&passwd=123%2Babc&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:35:58.362103+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:35:58.362] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=80.15.82.243:40715 2026-10-04T21:36:08.652332+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:36:08.652] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=80.15.82.243:41359 2026-10-04T21:36:08.969286+00:00 pl-waw-01 wings[761033]: ERROR: [Oct 4 21:36:08.969] sftp: failed to accept inbound connection error=[ssh: no auth passed yet, the credentials provided were invalid] ip=80.15.82.243:41354 ...
show less
Oct 4 21:02:30 isp sshd[4006353]: Failed password for root from 80.15.82.243 port 47266 ssh2
Oct 4 ...
show moreOct 4 21:02:30 isp sshd[4006353]: Failed password for root from 80.15.82.243 port 47266 ssh2
Oct 4 21:02:36 isp sshd[4006406]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.15.82.243 user=root
Oct 4 21:02:38 isp sshd[4006406]: Failed password for root from 80.15.82.243 port 47741 ssh2
...
show less
Web directory scan: 10 requests in 21h 28m (Last path: '/webapi/auth.cgi?account=tania&api=SYNO.API. ...
show moreWeb directory scan: 10 requests in 21h 28m (Last path: '/webapi/auth.cgi?account=tania&api=SYNO.API.Auth&format=sid&method=login&passwd=123&session=FileStation&version=6').
show less
User [scan] from [80.15.82.243] failed to sign in to [DSM] via [password] due to authorization failu ...
show moreUser [scan] from [80.15.82.243] failed to sign in to [DSM] via [password] due to authorization failure.
show less
Brute-Force
Anonymous
Web directory scan: 10 requests in 10h 14m (Last path: '/webapi/auth.cgi?account=hesabres&api=SYNO.A ...
show moreWeb directory scan: 10 requests in 10h 14m (Last path: '/webapi/auth.cgi?account=hesabres&api=SYNO.API.Auth&format=sid&method=login&passwd=123456&session=FileStation&version=6').
show less
Hacking
Web App Attack
Anonymous
Synology DSM password authentication brute-force activity; 2 failed login attempts observed in suppl ...
show moreSynology DSM password authentication brute-force activity; 2 failed login attempts observed in supplied log.
show less
Failed logins to a Synology NAS: 3 attempts via DSM, 2026-10-02 01:31 to 2026-10-02 07:02 UTC. 3 non ...
show moreFailed logins to a Synology NAS: 3 attempts via DSM, 2026-10-02 01:31 to 2026-10-02 07:02 UTC. 3 non-existent usernames tried.
show less
