This IP address has been reported a total of
149
times from
83 distinct
sources.
165.101.157.38 was first reported on
, and the most recent report was
.
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.
CrowdSec local HTTP alert
scenario: crowdsecurity/http-wordpress-scan
alert_id: 7356
events: 4
creat ...
show moreCrowdSec local HTTP alert
scenario: crowdsecurity/http-wordpress-scan
alert_id: 7356
events: 4
created_at: 2026-09-16T08:34:25Z
message: Ip 165.101.157.38 performed 'crowdsecurity/http-wordpress-scan' (4 events over 733.744921ms) at 2026-09-16 08:34:24.563420532 +0000 UTC
target_uri: ["/wp-login.php","/wordpress/wp-login.php","/site/wp-login.php","/cms/wp-login.php"]
method: ["GET"]
status: ["404"]
user_agent: ["Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0","Mozilla/5.0 (Android 14; Mobile; rv:128.0) Gecko/128.0 Firefox/128.0","Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36","Mozilla/5.0 (Macintosh; Intel Mac OS X 1
show less
Automated report: SSH brute force detected. This IP exceeded the allowed number of failed login atte ...
show moreAutomated report: SSH brute force detected. This IP exceeded the allowed number of failed login attempts (3 attempts).
show less
Sep 8 15:13:56 lnxmail62 sshd[3242993]: Connection reset by 165.101.157.38 port 51518
Sep 8 15:13: ...
show moreSep 8 15:13:56 lnxmail62 sshd[3242993]: Connection reset by 165.101.157.38 port 51518
Sep 8 15:13:57 lnxmail62 sshd[3242995]: Invalid user streamevenement from 165.101.157.38 port 51526
Sep 8 15:13:57 lnxmail62 sshd[3242995]: Invalid user streamevenement from 165.101.157.38 port 51526
...
show less
(sshd) Failed SSH login from 165.101.157.38 (IN/-/-): 5 in the last 3600 secs; Ports: *; Direction: ...
show more(sshd) Failed SSH login from 165.101.157.38 (IN/-/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 8 08:01:32 na-s3 sshd[3287314]: Invalid user vakantiewoningvressesursemois from 165.101.157.38 port 56068
Sep 8 08:13:34 na-s3 sshd[3408969]: Invalid user vakantiewoningvressesursemois from 165.101.157.38 port 52914
Sep 8 08:36:33 na-s3 sshd[3641567]: Invalid user vakantiewoningvressesursemois from 165.101.157.38 port 40824
Sep 8 08:48:10 na-s3 sshd[3758539]: Invalid user vakantiewoningvressesursemois from 165.101.157.38 port 55278
Sep 8 08:59:51 na-s3 sshd[3875219]: Invalid user vakantiewoningvressesursemois from 165.101.157.38 port 48934
show less
Sep 8 13:35:57 local sshd[15606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid= ...
show moreSep 8 13:35:57 local sshd[15606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.101.157.38
Sep 8 13:35:59 local sshd[15606]: Failed password for invalid user ubuntu from 165.101.157.38 port 35582 ssh2
Sep 8 13:42:39 local sshd[21971]: Failed password for root from 165.101.157.38 port 50530 ssh2
...
show less
Brute-Force
SSH
Showing 1 to
15
of 149 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩