IP Threat Report
20.214.157.214
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: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 278 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 59 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 98 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 36 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 108 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 217 | Medium-risk: admin panels, config files | +60 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 53 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 117 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 280 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 135 | Medium-risk: admin panels, config files | +60 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 33 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 145 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 72 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 295 | Medium-risk: admin panels, config files | +60 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 166 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 323 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 233 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 120 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 44 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 33 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 235 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 166 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 114 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 205 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 426 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 96 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 232 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 47 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 111 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 169 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 44 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 165 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 256 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 69 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 270 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 215 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 65 | Medium-risk: admin panels, config files | +60 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 301 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 664 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 227 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 341 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 158 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 442 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 104 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 421 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 222 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 443 | Medium-risk: admin panels, config files | +60 | |
| Burst: 48 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 222 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 108 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 223 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 41 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 138 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 249 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 84 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 194 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 149 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 63 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 267 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 305 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 661 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 109 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 164 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 273 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 271 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 80 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 400 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 152 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 91 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 228 | 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.214.157.214 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.214.157.214: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Traffic Flood Defense
IP 20.214.157.214 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🔎 Path Enumeration Protection
Block scanning from 20.214.157.214: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.214.157.214 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.214.157.214, located in Seoul, South Korea, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. The address has been active for 3 days in our monitoring system, producing 76 flagged requests at a rate of ~25.3/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. 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.
Related Threats
🇰🇷 Top threats from South Korea
4.217.180.34 (280)20.214.155.242 (280)52.231.66.246 (280)20.194.25.241 (280)20.196.195.121 (280)View all →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.
💡 GraphQL Security Risks
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.