This IP address has been reported a total of
71
times from
62 distinct
sources.
136.113.81.216 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 23
reports;
United States of America
with 17
reports;
Netherlands
with 8
reports.
The most common categories in these recent reports were:
Web App Attack
63
times;
Bad Web Bot
26
times;
Brute-Force
21
times;
Hacking
15
times;
Port Scan
3
times;
Other
4
times.
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.
Automated report: Unauthorized vulnerability scanning detected on 2026-10-27. 343 requests from this ...
show moreAutomated report: Unauthorized vulnerability scanning detected on 2026-10-27. 343 requests from this IP.
show less
(web_sensitive_file) srv101 Sensitive file probe (.env/.git/backup) 136.113.81.216 (US/United States ...
show more(web_sensitive_file) srv101 Sensitive file probe (.env/.git/backup) 136.113.81.216 (US/United States/216.81.113.136.bc.googleusercontent.com): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs:
show less
Automated web scanning detected by Wazuh (rule 100241): repeated 400/404 errors from mass probing of ...
show moreAutomated web scanning detected by Wazuh (rule 100241): repeated 400/404 errors from mass probing of admin/backdoor paths (e.g. wp-login.php, known CMS shell filenames) on an Apache web server, on 2026-10-27 16:34 UTC.
show less
