Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 45.139.104.161:
This IP address has been reported a total of
1,408
times from
155 distinct
sources.
45.139.104.161 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Czechia
with 2
reports;
Germany
with 2
reports;
United States of America
with 2
reports.
Over the same time period, 45.139.104.161 has changed
country of origin 2 times.
The most common categories in these recent reports were:
Web App Attack
9
times;
Hacking
4
times;
Brute-Force
2
times;
Bad Web Bot
2
times;
SQL Injection
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.
ActiveDefense automated detection: malicious HTTP scanning / exploit attempts. Signatures: aws_creds ...
show moreActiveDefense automated detection: malicious HTTP scanning / exploit attempts. Signatures: aws_creds. Observed by 1 sensor(s); 63 hits.
show less
Web App Attack
Anonymous
| [Dangerous/Philippines] Aggressive IP 45.139.104.161 (~30 hits). Type: DoS Defender- Web server 40 ...
show more| [Dangerous/Philippines] Aggressive IP 45.139.104.161 (~30 hits). Type: DoS Defender- Web server 400 error code
show less
Probing for secret files (.git, .env, credentials, database dumps, wp-config) | method: GET | path: ...
show moreProbing for secret files (.git, .env, credentials, database dumps, wp-config) | method: GET | path: /.aws/credentials | 2026-09-06 16:52 UTC
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-15T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-15T01:07:02+0100. Last: 2026-03-15T01:07:02+0100.
Samples:
- 2026-03-08 05:34:49,157 fail2ban.actions [739]: NOTICE [abuseipdb] Ban 45.139.104.161
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T21:07:02+0100. Last: 2026-03-14T21:07:02+0100.
Samples:
- 2026-03-08 05:34:49,157 fail2ban.actions [739]: NOTICE [abuseipdb] Ban 45.139.104.161
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T16:07:01+0100. Last: 2026-03-14T16:07:01+0100.
Samples:
- 2026-03-08 05:34:49,157 fail2ban.actions [739]: NOTICE [abuseipdb] Ban 45.139.104.161
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T11:07:02+0100. Last: 2026-03-14T11:07:02+0100.
Samples:
- 2026-03-08 05:34:49,157 fail2ban.actions [739]: NOTICE [abuseipdb] Ban 45.139.104.161
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-03-14T06:07:01+0100. Last: 2026-03-14T06:07:01+0100.
Samples:
- 2026-03-08 05:34:49,157 fail2ban.actions [739]: NOTICE [abuseipdb] Ban 45.139.104.161
show less