THREAT REPORT
IP Threat Report
20.210.128.125
ABUSE.MOM — BEHAVE OR GET EXPOSED
01
Geolocation & Classification
IP Address
20.210.128.125
Type
Hosting
Country
🇯🇵 Japan
City
Osaka
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (japanwest)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
7934
02
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 11/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 12/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 36/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 102 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 104 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 117 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 128 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 130 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 133 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 153 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 165 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 168 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 170 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 179 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 185 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 189 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 192 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 196 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 221 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 225 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 243 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 244 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 247 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 250 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 253 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 263 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 269 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 272 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 282 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 283 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 284 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 286 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 287 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 289 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 294 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 302 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 310 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 312 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 325 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 330 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 340 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 346 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 347 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 348 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 351 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 352 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 355 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 357 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 374 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 380 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 388 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 397 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 402 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 406 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 417 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 423 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 438 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 468 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 488 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 500 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 505 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 510 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 538 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 547 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 556 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 62 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 63 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 635 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 659 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 68 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 720 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 726 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 78 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 840 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 90 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 92 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 94 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 101 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 106 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 107 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 108 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 112 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 113 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 116 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 117 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 118 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 123 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 126 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 131 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 144 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 148 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 166 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 187 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 189 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 216 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 29 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 33 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 35 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 37 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 47 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 49 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 59 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 61 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 62 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 67 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 77 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 81 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 84 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 89 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 90 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 93 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 94 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 96 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 97 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 98 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Σ = 11315
03
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0
* Typical request patterns for detected signatures. Actual target domains are redacted.
04
Timeline
2026-10-03 08:11:53
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 11/2s (+35)
2026-10-11 01:06:42
Last malicious request observed
Total score reached: 310/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05
Network Provider
Microsoft Corporation
AS8075 · 🇯🇵 Japan
We have detected 1852 malicious IPs from this autonomous system.
06
Recommendations
Actions taken & recommended
- IP 20.210.128.125 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 20.210.128.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 20.210.128.125 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 20.210.128.125 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 Bot Detection
Address UA spoofing from 20.210.128.125: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
07
Neighbors in 20.210.128.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
09
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.spamcop.net
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
10
Threat Analysis
20.210.128.125 has been assigned a threat score of 310/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
Path EnumerationRequest FloodingUser-Agent Anomaly
📊 Threat Analysis
20.210.128.125 is registered in Osaka, Japan, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 7 days, this IP generated 7,934 malicious requests, averaging approximately 1133.4 requests per 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Japan currently accounts for 1,337 blocked IPs in our database, making it a major source of malicious traffic. At 310/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.
11
Related Threats
12
Security Intelligence
💡 DDoS Mitigation Approaches
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.
💡 Rate Limiting and Throttling Strategies
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.
🔍 Check Any IP Address
Share this report: