ABUSE.MOM
THREAT REPORT

IP Threat Report
20.210.131.207

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:48:15
First seen: 2026-07-01 00:28:03
Last seen: 2026-07-12 00:44:18
280

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 280/100. Total malicious requests observed: 693.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.210.131.207
Type
Hosting
Country
🇯🇵 Japan
City
Osaka
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (japanwest)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
693
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 25/10sAbnormally fast request rate — automated scanning+35
Burst 37/10sAbnormally fast request rate — automated scanning+35
Burst 40/10sAbnormally fast request rate — automated scanning+35
Burst 41/10sAbnormally fast request rate — automated scanning+35
Burst 42/10sAbnormally fast request rate — automated scanning+35
Burst 43/10sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 165Medium-risk: admin panels, config files+60
Danger medium hits: 220Medium-risk: admin panels, config files+60
Danger medium hits: 296Medium-risk: admin panels, config files+60
Danger medium hits: 318Medium-risk: admin panels, config files+60
Danger medium hits: 462Medium-risk: admin panels, config files+60
Danger medium hits: 518Medium-risk: admin panels, config files+60
Danger medium hits: 521Medium-risk: admin panels, config files+60
Danger medium hits: 526Medium-risk: admin panels, config files+60
Danger medium hits: 529Medium-risk: admin panels, config files+60
Danger medium hits: 617Medium-risk: admin panels, config files+60
Danger medium hits: 66Medium-risk: admin panels, config files+60
Danger medium hits: 711Medium-risk: admin panels, config files+60
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 130High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 155High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 177High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 38High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 39High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 81High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 93High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 1950
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-07-01 00:28:03
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 12/2s (+35), Burst 25/10s (+35)
2026-07-12 00:44:18
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 20.210.131.207 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

🔎 Directory Scan Defense

IP 20.210.131.207 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.131.207 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.131.207: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

20.210.131.207 has been assigned a threat score of 280/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

IP address 20.210.131.207 has been traced to Osaka, Japan, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 11 days, this IP generated 693 malicious requests, averaging approximately 63 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. Japan currently accounts for 106 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.

11

Related Threats

🇯🇵 Top threats from Japan

103.163.220.216 (340)35.189.151.182 (320)194.5.48.175 (305)34.97.45.15 (295)35.243.110.60 (288)View all →

🏢 Same network: AS8075

20.48.26.146 (280)52.140.193.66 (280)20.48.63.27 (280)104.46.220.175 (280)20.89.230.101 (280)View all →
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.

💡 State-Sponsored Cyber Operations

Nation-state actors conduct sophisticated campaigns for espionage, sabotage, and influence operations. Their resources exceed typical criminal organizations, enabling zero-day exploitation, long-term persistent access, and attacks on critical infrastructure.

🔍 Check Any IP Address

Share this report: