This IP address has been reported a total of
48
times from
42 distinct
sources.
45.139.24.30 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 12
reports;
United States of America
with 5
reports;
Netherlands
with 3
reports.
The most common categories in these recent reports were:
Brute-Force
30
times;
SSH
27
times;
Port Scan
4
times;
Hacking
2
times;
IoT Targeted
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.
2026-10-26T10:26:03.163804+02:00 slimbox sshd[2777408]: Failed password for root from 45.139.24.30 p ...
show more2026-10-26T10:26:03.163804+02:00 slimbox sshd[2777408]: Failed password for root from 45.139.24.30 port 53788 ssh2
2026-10-26T10:26:14.713833+02:00 slimbox sshd[2777410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
2026-10-26T10:26:17.022815+02:00 slimbox sshd[2777410]: Failed password for root from 45.139.24.30 port 58408 ssh2
...
show less
Brute-Force
SSH
Anonymous
2026-10-25T20:14:13.835702+02:00 PRACSNew sshd-session[1403069]: Failed password for root from 45.13 ...
show more2026-10-25T20:14:13.835702+02:00 PRACSNew sshd-session[1403069]: Failed password for root from 45.139.24.30 port 33178 ssh2
2026-10-25T20:14:26.775038+02:00 PRACSNew sshd-session[1403147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
2026-10-25T20:14:28.699304+02:00 PRACSNew sshd-session[1403147]: Failed password for root from 45.139.24.30 port 37542 ssh2
...
show less
Honeypot detection: port scan / service probe. 2 events observed. Reported automatically from a hone ...
show moreHoneypot detection: port scan / service probe. 2 events observed. Reported automatically from a honeypot sensor.
show less
2026-10-21T14:22:18.685653+00:00 arrow-at1 sshd-session[298602]: Failed password for root from 45.13 ...
show more2026-10-21T14:22:18.685653+00:00 arrow-at1 sshd-session[298602]: Failed password for root from 45.139.24.30 port 56546 ssh2
2026-10-21T14:22:31.768162+00:00 arrow-at1 sshd-session[298611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
2026-10-21T14:22:33.342143+00:00 arrow-at1 sshd-session[298611]: Failed password for root from 45.139.24.30 port 50018 ssh2
...
show less
Oct 17 18:31:37 Krasimir sshd[1268969]: Failed password for root from 45.139.24.30 port 51850 ssh2
O ...
show moreOct 17 18:31:37 Krasimir sshd[1268969]: Failed password for root from 45.139.24.30 port 51850 ssh2
Oct 17 18:31:49 Krasimir sshd[1268971]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
Oct 17 18:31:51 Krasimir sshd[1268971]: Failed password for root from 45.139.24.30 port 48114 ssh2
Oct 17 18:32:04 Krasimir sshd[1268974]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
Oct 17 18:32:06 Krasimir sshd[1268974]: Failed password for root from 45.139.24.30 port 55224 ssh2
Oct 17 18:32:18 Krasimir sshd[1268976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
Oct 17 18:32:20 Krasimir sshd[1268976]: Failed password for root from 45.139.24.30 port 57936 ssh2
...
show less
2026-10-10T00:01:59.756389+02:00 mail.vr9.pro sshd[425946]: Failed password for root from 45.139.24. ...
show more2026-10-10T00:01:59.756389+02:00 mail.vr9.pro sshd[425946]: Failed password for root from 45.139.24.30 port 38094 ssh2
2026-10-10T00:02:09.087743+02:00 mail.vr9.pro sshd[426668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.139.24.30 user=root
2026-10-10T00:02:10.740023+02:00 mail.vr9.pro sshd[426668]: Failed password for root from 45.139.24.30 port 43524 ssh2
...
show less
Honeypot trap triggered: unsolicited TCP connection(s) to unused port(s) 2222 on a host running no s ...
show moreHoneypot trap triggered: unsolicited TCP connection(s) to unused port(s) 2222 on a host running no such service. There is no legitimate reason to connect to these ports.
Observed 1 connection(s) from 2026-10-07T23:03:39Z to 2026-10-07T23:03:39Z UTC.
2026-10-07T23:03:39Z tcp/2222 connect, no payload (bare TCP probe)
Connection was blocked automatically at the firewall. Reported by an automated honeypot.
show less
Port Scan
Hacking
Brute-Force
IoT Targeted
Anonymous
Repeated failed SSH authentication attempts over TCP triggered a Fail2Ban ban.