This IP address has been reported a total of
23
times from
20 distinct
sources.
159.223.52.234 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Netherlands
with 6
reports;
United States of America
with 3
reports;
Germany
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
18
times;
Brute-Force
7
times;
Bad Web Bot
6
times;
Hacking
2
times;
Port Scan
2
times;
Other
3
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.
CrowdSec: probing for exposed secrets and config files. Scenario=crowdsecurity/http-sensitive-files; ...
show moreCrowdSec: probing for exposed secrets and config files. Scenario=crowdsecurity/http-sensitive-files; events=5; window=2026-10-14T20:11:36.288511248Z .. 2026-10-14T20:11:38.518585718Z. Tried: GET /.git/config | GET /.env | GET /.env.local | GET /.env.staging | GET /.env.development. Automated report, no manual review.
show less
Port scan against our edge firewall, detected by Wazuh: Regel 31151 | abuseipdb 83% (14 Meldungen, S ...
show morePort scan against our edge firewall, detected by Wazuh: Regel 31151 | abuseipdb 83% (14 Meldungen, SG)
show less
[ti-06al] Web exploit scanning: 1 suspicious requests detected by fail2ban jail apache-scanner. Exam ...
show more[ti-06al] Web exploit scanning: 1 suspicious requests detected by fail2ban jail apache-scanner. Example: 159.223.52.234 - - [13/Oct/2026:09:02:34 +0200] "GET /.git/config HTTP/1.1" 404 1350 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"
...
show less