This IP address has been reported a total of
147
times from
87 distinct
sources.
104.248.194.139 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
237 attempts since 08.12.2025 10:27:38 UTC - last one: 2025-12-08T14:02:33.944879+01:00 beta sshd-se ...
show more237 attempts since 08.12.2025 10:27:38 UTC - last one: 2025-12-08T14:02:33.944879+01:00 beta sshd-session[104800]: Connection closed by authenticating user mysql 104.248.194.139 port 43300 [preauth]
show less
Brute-Force
SSH
Anonymous
2025-12-08T07:51:49.261078-05:00 TWSAPROX sshd[2231463]: Invalid user nginx from 104.248.194.139 por ...
show more2025-12-08T07:51:49.261078-05:00 TWSAPROX sshd[2231463]: Invalid user nginx from 104.248.194.139 port 34078
2025-12-08T07:52:28.088832-05:00 TWSAPROX sshd[2231841]: Invalid user nginx from 104.248.194.139 port 35634
2025-12-08T07:53:07.866638-05:00 TWSAPROX sshd[2232230]: Invalid user nginx from 104.248.194.139 port 60808
2025-12-08T07:53:49.216226-05:00 TWSAPROX sshd[2232682]: Invalid user nginx from 104.248.194.139 port 33330
2025-12-08T07:54:27.239215-05:00 TWSAPROX sshd[2233070]: Invalid user nginx from 104.248.194.139 port 49888
2025-12-08T07:55:06.957675-05:00 TWSAPROX sshd[2233506]: Invalid user nginx from 104.248.194.139 port 43004
2025-12-08T07:55:43.760786-05:00 TWSAPROX sshd[2233896]: Invalid user nginx from 104.248.194.139 port 46998
2025-12-08T07:56:20.203575-05:00 TWSAPROX sshd[2234258]: Invalid user nginx from 104.248.194.139 port 59432
...
show less
2025-12-08T12:51:25.487425+00:00 0 sshd-session[192275]: Invalid user nginx from 104.248.194.139 por ...
show more2025-12-08T12:51:25.487425+00:00 0 sshd-session[192275]: Invalid user nginx from 104.248.194.139 port 45574
2025-12-08T12:52:04.253111+00:00 0 sshd-session[192277]: Invalid user nginx from 104.248.194.139 port 44312
2025-12-08T12:52:42.775447+00:00 0 sshd-session[192279]: Invalid user nginx from 104.248.194.139 port 47132
2025-12-08T12:53:22.929263+00:00 0 sshd-session[192281]: Invalid user nginx from 104.248.194.139 port 35060
2025-12-08T12:54:03.185322+00:00 0 sshd-session[192289]: Invalid user nginx from 104.248.194.139 port 53970
...
show less
2025-12-08T12:50:42.585252+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.24 ...
show more2025-12-08T12:50:42.585252+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.248.194.139 port 60354
2025-12-08T12:51:20.580858+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.248.194.139 port 41986
2025-12-08T12:51:59.478384+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.248.194.139 port 53538
2025-12-08T12:52:37.803142+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.248.194.139 port 57268
2025-12-08T12:53:17.678858+00:00 debian-4gb-hel1-2 701e1c2aebc4[921]: Invalid user nginx from 104.248.194.139 port 33550
...
show less
2025-12-08T12:48:38.667341+00:00 ubuntu sshd[646074]: Failed password for invalid user ftp from 104. ...
show more2025-12-08T12:48:38.667341+00:00 ubuntu sshd[646074]: Failed password for invalid user ftp from 104.248.194.139 port 44766 ssh2
2025-12-08T12:49:17.209028+00:00 ubuntu sshd[646078]: Invalid user ftp from 104.248.194.139 port 59472
2025-12-08T12:49:17.232942+00:00 ubuntu sshd[646078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.194.139
2025-12-08T12:49:18.980570+00:00 ubuntu sshd[646078]: Failed password for invalid user ftp from 104.248.194.139 port 59472 ssh2
2025-12-08T12:49:54.700710+00:00 ubuntu sshd[646082]: Invalid user ftp from 104.248.194.139 port 36562
...
show less
2025-12-08T12:47:53.007425+00:00 shy-frogs.aeza.network sshd[79054]: Failed password for invalid use ...
show more2025-12-08T12:47:53.007425+00:00 shy-frogs.aeza.network sshd[79054]: Failed password for invalid user ftp from 104.248.194.139 port 36940 ssh2
2025-12-08T12:48:31.506818+00:00 shy-frogs.aeza.network sshd[79113]: Invalid user ftp from 104.248.194.139 port 52024
2025-12-08T12:48:31.555878+00:00 shy-frogs.aeza.network sshd[79113]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.194.139
2025-12-08T12:48:33.654898+00:00 shy-frogs.aeza.network sshd[79113]: Failed password for invalid user ftp from 104.248.194.139 port 52024 ssh2
2025-12-08T12:49:11.940406+00:00 shy-frogs.aeza.network sshd[79157]: Invalid user ftp from 104.248.194.139 port 59960
...
show less
2025-12-08T20:36:04.938125+08:00 bird sshd[211319]: Failed password for invalid user ec2-user from 1 ...
show more2025-12-08T20:36:04.938125+08:00 bird sshd[211319]: Failed password for invalid user ec2-user from 104.248.194.139 port 58460 ssh2
2025-12-08T20:36:40.018074+08:00 bird sshd[211337]: Invalid user ec2-user from 104.248.194.139 port 43072
2025-12-08T20:36:40.304498+08:00 bird sshd[211337]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.194.139
2025-12-08T20:36:42.459787+08:00 bird sshd[211337]: Failed password for invalid user ec2-user from 104.248.194.139 port 43072 ssh2
2025-12-08T20:37:17.706502+08:00 bird sshd[211354]: Invalid user ec2-user from 104.248.194.139 port 44662
...
show less
2025-12-08T12:25:46.926821+00:00 0 sshd-session[191940]: Invalid user pi from 104.248.194.139 port 5 ...
show more2025-12-08T12:25:46.926821+00:00 0 sshd-session[191940]: Invalid user pi from 104.248.194.139 port 52040
2025-12-08T12:26:25.081761+00:00 0 sshd-session[191946]: Invalid user pi from 104.248.194.139 port 33404
2025-12-08T12:27:04.978245+00:00 0 sshd-session[191989]: Invalid user pi from 104.248.194.139 port 43662
2025-12-08T12:27:43.832382+00:00 0 sshd-session[191998]: Invalid user ec2-user from 104.248.194.139 port 56310
2025-12-08T12:28:23.020270+00:00 0 sshd-session[192011]: Invalid user ec2-user from 104.248.194.139 port 39468
...
show less
Brute-Force
SSH
Showing 1 to
15
of 147 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩