This IP address has been reported a total of
8
times from
6 distinct
sources.
217.181.83.13 was first reported on
March 3rd 2026 , and the most recent report was
1 week ago United States of America
with 2
reports;
Latvia
with 1
report;
Poland
with 1
report.
The most common categories in these recent reports were:
Web App Attack
4
times;
Hacking
2
times.
Old Reports
The most recent abuse report for this IP address is from
1 week ago
Reporter
IoA Timestamp (UTC)
Comment
Categories
🇺🇸
alsmanifesto
2026-09-24 16:26:30
(1 week ago)
Sent POST requests to a static site with no handler to receive them against fluentops.org. 1 request ...
show more
Sent POST requests to a static site with no handler to receive them against fluentops.org. 1 request, 2026-09-24 16:26:29 UTC. Blocked at our edge.
show less
Web App Attack
Hacking
🇺🇸
jfz-abuse
2026-09-04 15:57:54
(1 month ago)
fail2ban: apache-proxy
...
Web App Attack
🇵🇱
Budyn
2026-08-27 12:48:53
(1 month ago)
Automated threat detected by Budyn Honeypot Sinkhole. Attack type: CRITICAL: ModSecurity WAF Exploit ...
show more
Automated threat detected by Budyn Honeypot Sinkhole. Attack type: CRITICAL: ModSecurity WAF Exploit Block. Malicious scanner triggered a security trap targeting emulated vulnerabilities. Evidence: HOST: 51.83.237.XX | URI: /.git/HEAD | UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 | BODY: [Empty / GET Request]
show less
Hacking
Web App Attack
🇱🇻
garmtech.com
2026-08-16 05:45:48
(1 month ago)
IM360 WAF: Direct access to sensitive file or dotfile MV:/.env.production
Web App Attack
🇺🇸
ph
2026-04-26 21:22:35
(5 months ago)
Bad web bot attempting to run wp-login.php on non-WP site
Hacking
Bad Web Bot
Web App Attack
🇺🇸
TPI-Abuse
2026-03-13 15:31:04
(6 months ago)
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Port ...
show more
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Fri Mar 13 11:30:55.534841 2026] [security2:error] [pid 28032:tid 28032] [client 217.181.83.13:13266] ModSecurity: Access denied with code 403 (phase 2). Pattern match "\\\\b(close|keep-alive),[\\\\t\\\\n\\\\r ]{0,1}(close|keep-alive)\\\\b" at REQUEST_HEADERS:Connection. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/12_HTTP_Protocol.conf"] [line "70"] [id "210350"] [rev "1"] [msg "COMODO WAF: Multiple/Conflicting Connection Header Data Found||www.mfleetservice.com|F|4"] [data "keep-alive, close"] [severity "WARNING"] [tag "CWAF"] [tag "Protocol"] [hostname "www.mfleetservice.com"] [uri "/wp-login.php"] [unique_id "abQtr6G6LhlJPZ03XllmqgAAAAk"], referer: http://mfleetservice.com/wp-login.php
show less
Brute-Force
Bad Web Bot
Web App Attack
🇺🇸
TPI-Abuse
2026-03-12 18:11:05
(6 months ago)
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Port ...
show more
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Thu Mar 12 14:10:53.839236 2026] [security2:error] [pid 10693:tid 10693] [client 217.181.83.13:58512] ModSecurity: Access denied with code 403 (phase 2). Pattern match "\\\\b(close|keep-alive),[\\\\t\\\\n\\\\r ]{0,1}(close|keep-alive)\\\\b" at REQUEST_HEADERS:Connection. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/12_HTTP_Protocol.conf"] [line "70"] [id "210350"] [rev "1"] [msg "COMODO WAF: Multiple/Conflicting Connection Header Data Found||www.gemco-mfg.com|F|4"] [data "keep-alive, close"] [severity "WARNING"] [tag "CWAF"] [tag "Protocol"] [hostname "www.gemco-mfg.com"] [uri "/wp-login.php"] [unique_id "abMBrSkgI_4MPldLNUlejgAAAAc"], referer: https://www.gemco-mfg.com/wp-login.php
show less
Brute-Force
Bad Web Bot
Web App Attack
🇺🇸
TPI-Abuse
2026-03-03 10:33:53
(7 months ago)
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Port ...
show more
(mod_security) mod_security (id:210350) triggered by 217.181.83.13 (-): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Tue Mar 03 05:33:44.039957 2026] [security2:error] [pid 17687:tid 17687] [client 217.181.83.13:59368] ModSecurity: Access denied with code 403 (phase 2). Pattern match "\\\\b(close|keep-alive),[\\\\t\\\\n\\\\r ]{0,1}(close|keep-alive)\\\\b" at REQUEST_HEADERS:Connection. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/12_HTTP_Protocol.conf"] [line "70"] [id "210350"] [rev "1"] [msg "COMODO WAF: Multiple/Conflicting Connection Header Data Found||iconconstructors.com|F|4"] [data "keep-alive, close"] [severity "WARNING"] [tag "CWAF"] [tag "Protocol"] [hostname "iconconstructors.com"] [uri "/wp-login.php"] [unique_id "aaa5CBlVq25WmXYe3gfhOwAAAAs"], referer: http://iconconstructors.com/wp-login.php
show less
Brute-Force
Bad Web Bot
Web App Attack
Showing 1 to
8
of 8 reports
