This IP address has been reported a total of
40
times from
30 distinct
sources.
34.142.101.124 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 8
reports;
Netherlands
with 6
reports.
The most common categories in these recent reports were:
Web App Attack
35
times;
Brute-Force
20
times;
Bad Web Bot
15
times;
Hacking
9
times;
SSH
1
time;
Other
1
time.
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.
CrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban tri ...
show moreCrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban triggered. Detection time (UTC): 2026-10-24T06:28:11.942070117Z. Context: http_status=503
show less
3 incidents: web scanning/attack. First: 2026-10-24 01:55, Last: 2026-10-24 01:55 UTC. Triggers: ngi ...
show more3 incidents: web scanning/attack. First: 2026-10-24 01:55, Last: 2026-10-24 01:55 UTC. Triggers: nginx-noscript,nginx-botsearch,nginx-botsearch.
show less
Mass vulnerability scanning (LFI / path traversal probes with query parameters such as lokasie=/proc ...
show moreMass vulnerability scanning (LFI / path traversal probes with query parameters such as lokasie=/proc/...) against a production server. Observed on 1 day(s) between 2026-10-24 and 2026-10-24 (UTC). Additional activity: badscanner. Sample request: GET /.env.staging HTTP/1.1
show less
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-20.
show less
