
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 107/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 144/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 145/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 94/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 99/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 241 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 302 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 337 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 362 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 25 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 35 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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 4.207.145.86: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 4.207.145.86.
IP 4.207.145.86 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.
4.207.145.86 has been assigned a threat score of 280/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 4.207.145.86 has been traced to Dublin, Ireland, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1,473 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~245.5 requests per 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. At 280/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.
Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.