
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 10/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 12/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 15/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 36/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 52/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 55/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 121 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 170 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 196 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 209 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 219 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 273 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 319 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 341 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 402 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 41 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 420 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 453 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 462 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 478 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 489 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 496 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 502 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 509 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 528 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 533 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 539 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 556 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 587 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 592 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 615 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 618 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 619 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 620 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 621 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 67 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 95 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
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.
IP 54.200.80.123 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
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:
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.
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 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.