This IP address has been reported a total of
135
times from
23 distinct
sources.
104.207.52.237 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.
(mod_security) mod_security (id:225170) triggered by 104.207.52.237 (-): 1 in the last 300 secs; Por ...
show more(mod_security) mod_security (id:225170) triggered by 104.207.52.237 (-): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Tue Apr 08 17:27:01.667586 2025] [security2:error] [pid 29034:tid 29101] [client 104.207.52.237:10833] [client 104.207.52.237] ModSecurity: Access denied with code 403 (phase 2). Operator EQ matched 0 at REQUEST_COOKIES_NAMES. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/26_Apps_WordPress.conf"] [line "155"] [id "225170"] [rev "3"] [msg "COMODO WAF: Sensitive Information Disclosure Vulnerability in WordPress 4.7 (CVE-2017-5487)||driftwoodblue.com|F|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "WordPress"] [hostname "driftwoodblue.com"] [uri "/wp-json/wp/v2/users"] [unique_id "Z_WUpYF9APDgibwN0-hHgAAAABI"], referer: https://www.google.com
show less
Brute-Force
Bad Web Bot
Web App Attack
Anonymous
Attempted brute force login to web vpn 4 time(s); last attempt for 2025.04.06 is noted in report tim ...
show moreAttempted brute force login to web vpn 4 time(s); last attempt for 2025.04.06 is noted in report timestamp
show less
Hacking
Brute-Force
Showing 1 to
15
of 135 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown ๐ฉ