IP Threat Report
20.151.220.171
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 129 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 296 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 199 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 123 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 553 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 98 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 321 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 368 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 322 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 87 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 86 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 23 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 131 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 484 | Medium-risk: admin panels, config files | +60 | |
| Burst: 78 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 62 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 94 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 543 | Medium-risk: admin panels, config files | +60 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 20.151.220.171 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
🤖 Bot Detection
Address UA spoofing from 20.151.220.171: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Path Enumeration Protection
Block scanning from 20.151.220.171: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.151.220.171.
Blacklist Status (DNSBL)
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.
Threat Analysis
20.151.220.171 has been assigned a threat score of 280/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 20.151.220.171, located in Toronto, Canada, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 16 flagged requests at a rate of ~16/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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 110 flagged addresses, Canada represents a significant presence in our threat database. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Related Threats
Security Intelligence
💡 HTTP Header Analysis for Threat Detection
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.
💡 GDPR and Threat Intelligence
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.