This IP address has been reported a total of
154
times from
123 distinct
sources.
42.93.165.20 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.
2024-08-03 07:32:25 server sshd[5352]: Failed password for invalid user suporte from 42.93.165.20 po ...
show more2024-08-03 07:32:25 server sshd[5352]: Failed password for invalid user suporte from 42.93.165.20 port 3939 ssh2
show less
Aug 4 17:36:39 alertalicitacao sshd[1562202]: Invalid user wpyan from 42.93.165.20 port 1335
Aug 4 ...
show moreAug 4 17:36:39 alertalicitacao sshd[1562202]: Invalid user wpyan from 42.93.165.20 port 1335
Aug 4 17:41:06 alertalicitacao sshd[1562908]: Invalid user sv from 42.93.165.20 port 3868
Aug 4 17:42:14 alertalicitacao sshd[1563089]: Invalid user courtney from 42.93.165.20 port 1532
Aug 4 17:43:53 alertalicitacao sshd[1563310]: Invalid user stafi from 42.93.165.20 port 2074
Aug 4 17:44:25 alertalicitacao sshd[1563388]: Invalid user mvk from 42.93.165.20 port 5067
...
show less
DATE:2024-08-04 16:43:47, IP:42.93.165.20, PORT:ssh SSH brute force auth (docker-dc)
Brute-Force
SSH
Anonymous
Aug 4 09:28:53 raspberrypi sshd[5416]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ...
show moreAug 4 09:28:53 raspberrypi sshd[5416]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.93.165.20
Aug 4 09:28:56 raspberrypi sshd[5416]: Failed password for invalid user poker from 42.93.165.20 port 4131 ssh2
Aug 4 09:29:36 raspberrypi sshd[5419]: Failed password for root from 42.93.165.20 port 3349 ssh2
Aug 4 09:30:18 raspberrypi sshd[5423]: Failed password for root from 42.93.165.20 port 2626 ssh2
Aug 4 09:30:56 raspberrypi sshd[5426]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.93.165.20
Aug 4 09:30:58 raspberrypi sshd[5426]: Failed password for invalid user konstantin from 42.93.165.20 port 1829 ssh2
show less
2024-08-04T16:36:32.973810 singularity2 sshd[1967862]: Connection from 42.93.165.20 port 1714 on 10. ...
show more2024-08-04T16:36:32.973810 singularity2 sshd[1967862]: Connection from 42.93.165.20 port 1714 on 10.0.0.7 port 2222 rdomain ""
2024-08-04T16:36:34.268751 singularity2 sshd[1967862]: Invalid user test from 42.93.165.20 port 1714
2024-08-04T16:36:34.592251 singularity2 sshd[1967862]: Disconnected from invalid user test 42.93.165.20 port 1714 [preauth]
2024-08-04T16:37:11.683798 singularity2 sshd[1967884]: Connection from 42.93.165.20 port 4454 on 10.0.0.7 port 2222 rdomain ""
2024-08-04T16:37:13.722732 singularity2 sshd[1967884]: Invalid user forest from 42.93.165.20 port 4454
...
show less
DNS Compromise
DNS Poisoning
Fraud Orders
DDoS Attack
FTP Brute-Force
Ping of Death
Phishing
Fraud VoIP
Open Proxy
Web Spam
Email Spam
Blog Spam
VPN IP
Port Scan
Hacking
SQL Injection
Spoofing
Brute-Force
Bad Web Bot
Exploited Host
Web App Attack
SSH
IoT Targeted
2024-08-04T11:09:41.354373+02:00 nc2.motyka.pro sshd[2837906]: Invalid user pk from 42.93.165.20 por ...
show more2024-08-04T11:09:41.354373+02:00 nc2.motyka.pro sshd[2837906]: Invalid user pk from 42.93.165.20 port 2317
2024-08-04T11:09:41.358156+02:00 nc2.motyka.pro sshd[2837906]: Failed password for invalid user pk from 42.93.165.20 port 2317 ssh2
2024-08-04T11:10:58.236813+02:00 nc2.motyka.pro sshd[2840442]: Invalid user mateo from 42.93.165.20 port 3811
2024-08-04T11:10:58.240347+02:00 nc2.motyka.pro sshd[2840442]: Failed password for invalid user mateo from 42.93.165.20 port 3811 ssh2
2024-08-04T11:11:34.277831+02:00 nc2.motyka.pro sshd[2841753]: Invalid user lls from 42.93.165.20 port 2361
...
show less
Aug 4 19:03:31 ip-172-26-5-63 sshd[849890]: Invalid user dns from 42.93.165.20 port 3796
Aug 4 19: ...
show moreAug 4 19:03:31 ip-172-26-5-63 sshd[849890]: Invalid user dns from 42.93.165.20 port 3796
Aug 4 19:09:16 ip-172-26-5-63 sshd[850520]: Invalid user sw from 42.93.165.20 port 1206
Aug 4 19:09:59 ip-172-26-5-63 sshd[850522]: Invalid user pk from 42.93.165.20 port 4112
...
show less
Aug 4 06:35:45 cloud sshd[215549]: Invalid user wmm from 42.93.165.20 port 2861
Aug 4 06:46:42 clo ...
show moreAug 4 06:35:45 cloud sshd[215549]: Invalid user wmm from 42.93.165.20 port 2861
Aug 4 06:46:42 cloud sshd[215973]: Invalid user souken from 42.93.165.20 port 2457
Aug 4 06:47:59 cloud sshd[215993]: Invalid user mtc from 42.93.165.20 port 1727
Aug 4 06:49:05 cloud sshd[216015]: Invalid user zp from 42.93.165.20 port 4060
Aug 4 06:51:26 cloud sshd[216061]: Invalid user kabi from 42.93.165.20 port 4676
show less
Brute-Force
SSH
Anonymous
2024-08-04T06:31:50+02:00 lb-2 sshd[187093]: Failed password for invalid user wmm from 42.93.165.20 ...
show more2024-08-04T06:31:50+02:00 lb-2 sshd[187093]: Failed password for invalid user wmm from 42.93.165.20 port 4491 ssh2
2024-08-04T06:41:25+02:00 lb-2 sshd[187581]: Invalid user haijun from 42.93.165.20 port 1357
2024-08-04T06:41:25+02:00 lb-2 sshd[187581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.93.165.20
2024-08-04T06:41:26+02:00 lb-2 sshd[187581]: Failed password for invalid user haijun from 42.93.165.20 port 1357 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 154 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩