ABUSE.MOM
THREAT REPORT

IP Threat Report
54.200.80.123

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:51:35
First seen: 2026-05-25 06:04:44
Last seen: 2026-05-30 10:47:39
203

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404
01

Geolocation & Classification

IP Address
54.200.80.123
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
8824
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 22/10sAbnormally fast request rate — automated scanning+35
Burst 28/10sAbnormally fast request rate — automated scanning+35
Burst 32/10sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 38/10sAbnormally fast request rate — automated scanning+35
Burst 39/10sAbnormally fast request rate — automated scanning+35
Burst 40/10sAbnormally fast request rate — automated scanning+35
Burst 41/10sAbnormally fast request rate — automated scanning+35
Burst 43/10sAbnormally fast request rate — automated scanning+35
Burst 45/10sAbnormally fast request rate — automated scanning+35
Burst 46/10sAbnormally fast request rate — automated scanning+35
Burst 47/10sAbnormally fast request rate — automated scanning+35
Burst 48/10sAbnormally fast request rate — automated scanning+35
Burst 49/10sAbnormally fast request rate — automated scanning+35
Burst 50/10sAbnormally fast request rate — automated scanning+35
Burst 51/10sAbnormally fast request rate — automated scanning+35
Burst 52/10sAbnormally fast request rate — automated scanning+35
Burst 53/10sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 55/10sAbnormally fast request rate — automated scanning+35
Burst 56/10sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Burst 58/10sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 121High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 170High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 196High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 209High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 219High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 273High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 319High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 341High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 402High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 41High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 420High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 453High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 462High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 478High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 489High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 496High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 502High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 509High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 528High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 533High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 539High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 55High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 556High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 587High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 592High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 615High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 618High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 619High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 620High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 621High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 67High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 95High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 4383
03

Observed Activity

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

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

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

04

Timeline

2026-05-25 06:04:44
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 10/2s (+35), Burst 12/2s (+35)
2026-05-30 10:47:39
Last malicious request observed
Total score reached: 203/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.200.80.123 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

🔎 Path Enumeration Protection

Block scanning from 54.200.80.123: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

IP 54.200.80.123 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

54.200.80.123 has been assigned a threat score of 203/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

IP address 54.200.80.123 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. The address has been active for 5 days in our monitoring system, producing 8,824 flagged requests at a rate of ~1764.8/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and Request Flooding), 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. At 203/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Satellite Internet Security

Satellite internet introduces unique security challenges including high latency that affects real-time threat detection, shared bandwidth that enables traffic sniffing, and coverage areas that cross multiple jurisdictions complicating legal response.

🔍 Check Any IP Address

Share this report: