
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 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 19/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/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 51/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 52/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 155 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 170 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 209 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 44 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 548 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 585 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 599 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 608 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 610 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 617 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 618 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 621 | 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.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 18.225.11.43.
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.
18.225.11.43 has been assigned a threat score of 178/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:
The address 18.225.11.43 originates from Dublin, United States, operating on the network of Amazon.com, Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 59 flagged requests at a rate of ~59/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 130 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 178/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.
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.