This IP address has been reported a total of
38
times from
27 distinct
sources.
136.69.138.30 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 12
reports;
Germany
with 9
reports;
Netherlands
with 5
reports.
The most common categories in these recent reports were:
Web App Attack
35
times;
Bad Web Bot
18
times;
Brute-Force
12
times;
Hacking
6
times;
Exploited Host
2
times;
Other
2
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.
Auto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on ...
show moreAuto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on 2026-10-13.
show less
(secretscan) Secret-Scanner (env/git/ssh/credentials) from 136.69.138.30 (US/United States/30.138.69 ...
show more(secretscan) Secret-Scanner (env/git/ssh/credentials) from 136.69.138.30 (US/United States/30.138.69.136.bc.googleusercontent.com)
show less
Probed planted web canary URI (not a real app path).
HTTP request completed against planted URIs (.e ...
show moreProbed planted web canary URI (not a real app path).
HTTP request completed against planted URIs (.env/wp-login/xmlrpc/phpmyadmin/.git).
jail=nginx-canary proto=tcp port=80,443 failures>=2 class=web-app-probe
these paths are not real apps on this host; hit is hostile recon
when=2026-10-13T19:55:30Z sensor=fail2ban role=web-canary
src=136.69.138.30
show less
(mod_security) mod_security (id:949110) triggered by 136.69.138.30 (US/United States/30.138.69.136.b ...
show more(mod_security) mod_security (id:949110) triggered by 136.69.138.30 (US/United States/30.138.69.136.bc.googleusercontent.com): N in the last X secs
show less
