This IP address has been reported a total of
1,806
times from
570 distinct
sources.
178.16.54.137 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.
178.16.54.137 - - [14/Jul/2026:01:31:05 +0100] 443 "GET /.env HTTP/2.0" 301 1274 "-" "Mozilla/5.0 (M ...
show more178.16.54.137 - - [14/Jul/2026:01:31:05 +0100] 443 "GET /.env HTTP/2.0" 301 1274 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko, Yokohama Institute of Information Security https://www.iisec.ac.jp) Chrome/124.0.0.0 Safari/537.36"
...
show less
178.16.54.137 - Recidivist IP still active after blacklisting. Reported from IIS access logs on 2026 ...
show more178.16.54.137 - Recidivist IP still active after blacklisting. Reported from IIS access logs on 2026-08-11.
show less
WAF block action triggered by rule set "Version Control - Information Disclosure" (696 occurrences o ...
show moreWAF block action triggered by rule set "Version Control - Information Disclosure" (696 occurrences observed).
show less
Attack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyA ...
show moreAttack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyAdmin, etc.). Detected + blocked by fail2ban / nginx / firewall. Automated report.
show less
Attack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyA ...
show moreAttack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyAdmin, etc.). Detected + blocked by fail2ban / nginx / firewall. Automated report.
show less
Attack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyA ...
show moreAttack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyAdmin, etc.). Detected + blocked by fail2ban / nginx / firewall. Automated report.
show less
Attack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyA ...
show moreAttack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyAdmin, etc.). Detected + blocked by fail2ban / nginx / firewall. Automated report.
show less
Suricata Detected 2 attacks from 178.16.54.137.; ET DROP Spamhaus DROP Listed Traffic Inbound group ...
show moreSuricata Detected 2 attacks from 178.16.54.137.; ET DROP Spamhaus DROP Listed Traffic Inbound group 36; IP: 178.16.54.137; Ports: 59334; Direction: to_server; Trigger: DROP; Category: Misc Attack; Severity: 2
show less
178.16.54.137 - Recidivist IP still active after blacklisting. Reported from IIS access logs on 2026 ...
show more178.16.54.137 - Recidivist IP still active after blacklisting. Reported from IIS access logs on 2026-08-01.
show less
Attack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyA ...
show moreAttack against a personal web server: HTTP scanning for common exploit paths (wp-login, .env, phpMyAdmin, etc.). Detected + blocked by fail2ban / nginx / firewall. Automated report.
show less
Web App Attack
Bad Web Bot
Showing 1 to
15
of 1806 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩