Log in to view charts and search reports for this IP.
Log In
Reports Activity
Example preview
Report Categories (Last 60 Days)
Example preview
Top Reporter Countries (Last 60 Days)
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 120.48.80.84
This IP address has been reported a total of
60
times from
55 distinct
sources.
120.48.80.84 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 17
reports;
United States of America
with 13
reports;
Finland
with 5
reports.
The most common categories in these recent reports were:
SSH
55
times;
Brute-Force
55
times;
Port Scan
4
times;
Hacking
4
times;
Bad Web Bot
1
time.
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.
Automated honeypot observation: SSH brute-force / credential-stuffing. Failed logins: 1, successful: ...
show moreAutomated honeypot observation: SSH brute-force / credential-stuffing. Failed logins: 1, successful: 0, commands: 0, file transfers: 0. Seen on 1 sensor(s) (ap1) over 2026-09-22..2026-09-22. Reported by an SSH honeypot network; no production service involved.
show less
2026-09-22T21:11:28.604251 redacted sshd[353864]: pam_unix(sshd:auth): authentication failure; logna ...
show more2026-09-22T21:11:28.604251 redacted sshd[353864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.48.80.84
2026-09-22T21:11:30.719312 redacted sshd[353864]: Failed password for invalid user mas from 120.48.80.84 port 34666 ssh2
2026-09-22T21:15:28.472141 redacted sshd[353881]: User root from 120.48.80.84 not allowed because not listed in AllowUsers
show less
Sep 22 13:45:45 vpn sshd[4156856]: Invalid user wms from 120.48.80.84 port 37488
Sep 22 13:53:18 vpn ...
show moreSep 22 13:45:45 vpn sshd[4156856]: Invalid user wms from 120.48.80.84 port 37488
Sep 22 13:53:18 vpn sshd[4158266]: User root from 120.48.80.84 not allowed because not listed in AllowUsers
Sep 22 14:05:30 vpn sshd[4160625]: Invalid user visitor from 120.48.80.84 port 37530
...
show less
2026-09-22T07:45:28.175500-04:00 neptune.izeug.com sshd[3362815]: Failed password for invalid user w ...
show more2026-09-22T07:45:28.175500-04:00 neptune.izeug.com sshd[3362815]: Failed password for invalid user wms from 120.48.80.84 port 35974 ssh2
2026-09-22T07:53:15.161113-04:00 neptune.izeug.com sshd[3363242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.48.80.84 user=root
2026-09-22T07:53:17.341305-04:00 neptune.izeug.com sshd[3363242]: Failed password for root from 120.48.80.84 port 35984 ssh2
...
show less
Unsolicited SSH brute-force against port 22 on my small self-hosted server. 6 failed authentication ...
show moreUnsolicited SSH brute-force against port 22 on my small self-hosted server. 6 failed authentication attempts inside the fail2ban detection window triggered an automatic ban (jail sshd). Publickey-only auth means no attempt here could have succeeded -- this is untargeted scanning. Repeat offenses from this address get exponentially longer bans. Reported automatically by fail2ban; no manual review.
show less
2026-09-22T08:13:46.872559 yip.floofy.tech sshd-session[2274082]: Failed password for invalid user b ...
show more2026-09-22T08:13:46.872559 yip.floofy.tech sshd-session[2274082]: Failed password for invalid user bot from 120.48.80.84 port 41986 ssh2
2026-09-22T08:29:24.975216 yip.floofy.tech sshd-session[2281353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.48.80.84 user=root
2026-09-22T08:29:27.616575 yip.floofy.tech sshd-session[2281353]: Failed password for root from 120.48.80.84 port 42036 ssh2
...
show less
