This IP address has been reported a total of
62
times from
46 distinct
sources.
34.180.122.46 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 23
reports;
Netherlands
with 10
reports;
United States of America
with 9
reports.
The most common categories in these recent reports were:
Web App Attack
48
times;
Bad Web Bot
20
times;
Brute-Force
19
times;
Hacking
12
times;
DDoS Attack
2
times;
Other
5
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.
Web scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ba ...
show moreWeb scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ban.
show less
Automated web vulnerability scanning: 120 HTTP 4xx probes for sensitive paths (/%2Fadmin, /%2Fapi/co ...
show moreAutomated web vulnerability scanning: 120 HTTP 4xx probes for sensitive paths (/%2Fadmin, /%2Fapi/config, /%2Fsettings, /.bashrc). Detected by Wazuh HIDS rule 31151 on a self-hosted web server.
show less
[AUTORAVALT][[09/10/2026 - 00:53:33 -03:00 UTC]
Attack from [Google LLC]
[34.180.122.46][46.122.180. ...
show more[AUTORAVALT][[09/10/2026 - 00:53:33 -03:00 UTC]
Attack from [Google LLC]
[34.180.122.46][46.122.180.34.bc.googleusercontent.com]
Action: BLocKed
Hacking... Unauthorized attempts to access the server.
Web App Attack -> Attempts to probe for or exploit installed web applications such as a CMS like WordPress/Drupal, e-commerce solutions, forum software, phpMyAdm]
...
show less
Web scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ba ...
show moreWeb scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ban.
show less
