ABUSE.MOM
THREAT REPORT

IP Threat Report
20.189.200.150

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:48:15
First seen: 2026-07-08 14:45:17
Last seen: 2026-07-12 00:58:00
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 23/2sAbnormally fast request rate — automated scanning+35
Burst 24/2sAbnormally fast request rate — automated scanning+35
Burst 32/10sAbnormally fast request rate — automated scanning+35
Burst 37/10sAbnormally fast request rate — automated scanning+35
Burst 38/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 79/10sAbnormally fast request rate — automated scanning+35
Burst 83/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 213Medium-risk: admin panels, config files+60
Danger medium hits: 381Medium-risk: admin panels, config files+60
Danger medium hits: 422Medium-risk: admin panels, config files+60
Danger medium hits: 423Medium-risk: admin panels, config files+60
Danger medium hits: 425Medium-risk: admin panels, config files+60
Danger medium hits: 426Medium-risk: admin panels, config files+60
Danger medium hits: 47Medium-risk: admin panels, config files+60
Danger medium hits: 634Medium-risk: admin panels, config files+60
Danger medium hits: 639Medium-risk: admin panels, config files+60
Danger medium hits: 697Medium-risk: admin panels, config files+60
Danger medium hits: 850Medium-risk: admin panels, config files+60
Danger medium hits: 852Medium-risk: admin panels, config files+60
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 1750
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-08 14:45:17
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 10/2s (+35)
2026-07-12 00:58:00
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.189.200.150 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.189.200.150 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.189.200.150.

🤖 Bot Detection

Address UA spoofing from 20.189.200.150: 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
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

20.189.200.150 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 20.189.200.150 to malicious activity originating from Osaka, Japan, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 3 days, this IP generated 1,338 malicious requests, averaging approximately 446 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. With 106 flagged addresses, Japan 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.

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.

💡 Log Correlation and SIEM Integration

Correlating logs across web servers, firewalls, DNS, and authentication systems reveals attack patterns invisible in individual log sources. Modern SIEM platforms use statistical analysis to connect related events across time and systems.

🔍 Check Any IP Address

Share this report: