IP Threat Report
20.210.88.198
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: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 46 | Medium-risk: admin panels, config files | +60 | |
| 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: 351 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 698 | Medium-risk: admin panels, config files | +60 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 76 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 42 | Medium-risk: admin panels, config files | +60 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 106 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 572 | Medium-risk: admin panels, config files | +60 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 48 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 333 | Medium-risk: admin panels, config files | +60 | |
| 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: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 63 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 302 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 79 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 294 | Medium-risk: admin panels, config files | +60 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 183 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 198 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 441 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 49 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 293 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 439 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 381 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 113 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 400 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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.210.88.198 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.210.88.198: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.210.88.198.
🔎 Directory Scan Defense
IP 20.210.88.198 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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.210.88.198 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
IP address 20.210.88.198 has been traced to Tokyo, Japan, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 23 hostile requests from this IP — roughly 7.7 per day on average. 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Japan currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 280/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.
Related Threats
Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Certificate Transparency Monitoring
Certificate Transparency logs record all publicly trusted TLS certificates. Monitoring these logs reveals unauthorized certificate issuance, phishing domain preparation, and shadow IT — providing early warning of attacks targeting an organizations domain.