ABUSE.MOM
THREAT REPORT

IP Threat Report
54.189.141.224

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 19:57:57
First seen: 2026-04-08 18:00:05
Last seen: 2026-04-08 18:00:05
125

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 125/100. Total malicious requests observed: 1.

BOT_UADANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
54.189.141.224
Type
Hosting
Country
🇺🇸 United States
City
Portland
ISP
Amazon.com, Inc.
Organization
AWS EC2 (us-west-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 125
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-08 18:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), Danger strong hits: 2 (+50), 404 ratio 40-60% (+15)
2026-04-08 18:00:05
Last malicious request observed
Total score reached: 125/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS16509 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 54.189.141.224 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 54.189.141.224 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Directory Scan Defense

IP 54.189.141.224 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

54.189.141.224 has been assigned a threat score of 125/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

IP address 54.189.141.224 has been traced to Portland, United States, operating on the network of Amazon.com, Inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 130 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 125/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS16509

15.220.152.241 (320)18.219.106.176 (315)15.220.169.114 (280)108.136.131.13 (265)54.206.58.169 (263)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 DNS-Based Threat Detection

Monitoring DNS queries reveals malicious activity including command-and-control communication, data exfiltration through DNS tunneling, and connections to known malicious domains. DNS is often the first indicator of compromise in network forensics.

🔍 Check Any IP Address

Share this report: