ABUSE.MOM
THREAT REPORT

IP Threat Report
20.89.241.129

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:08:40
First seen: 2026-03-01 02:00:06
Last seen: 2026-03-17 22:00:09
255

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404UA_SUSREDIRECT_PROBE
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 39Medium-risk: admin panels, config files+60
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 43 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 42 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 26Medium-risk: admin panels, config files+60
Burst: 33 req / 10sAbnormally fast request rate — automated scanning+35
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 3Medium-risk: admin panels, config files+30
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 845
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-03-01 02:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 9 (+100), Danger medium hits: 39 (+60), Burst: 12 req / 2s (+35)
2026-03-17 22:00:09
Last malicious request observed
Total score reached: 255/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.89.241.129 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.89.241.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

IP 20.89.241.129 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.89.241.129: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 20.89.241.129: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 20.89.241.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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

20.89.241.129 has been assigned a threat score of 255/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:

Request FloodingPath EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 20.89.241.129 originates from Osaka, Japan, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 16 days in our monitoring system, producing 28 flagged requests at a rate of ~1.8/day. 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. Our records show 101 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. With a threat score of 255/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.243.110.60 (288)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)View all →

🏢 Same network: AS8075

74.241.249.229 (340)20.151.111.128 (308)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

🔍 Check Any IP Address

Share this report: