ABUSE.MOM
THREAT REPORT

IP Threat Report
20.89.56.154

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:14:42
First seen: 2026-02-17 17:25:06
Last seen: 2026-02-18 20:00:05
280

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHRATIO_404REDIRECT_PROBEBURSTIMPORT
01

Geolocation & Classification

IP Address
20.89.56.154
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (japaneast)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
20
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 50High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 383Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 41 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 100High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 574Medium-risk: admin panels, config files+60
Burst: 42 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 108Medium-risk: admin panels, config files+60
Danger medium hits: 385Medium-risk: admin panels, config files+60
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 78High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 585Medium-risk: admin panels, config files+60
Danger medium hits: 516Medium-risk: admin panels, config files+60
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 120Medium-risk: admin panels, config files+60
Danger strong hits: 75High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 376Medium-risk: admin panels, config files+60
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 213Medium-risk: admin panels, config files+60
Danger strong hits: 39High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 215Medium-risk: admin panels, config files+60
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Σ = 1615
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-02-17 17:25:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 50 (+100), Danger medium hits: 383 (+60)
2026-02-18 20:00:05
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.89.56.154 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.89.56.154: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Directory Scan Defense

IP 20.89.56.154 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 20.89.56.154 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

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.56.154 has been assigned a threat score of 280/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

The address 20.89.56.154 originates from Tokyo, Japan, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 20 malicious requests, averaging approximately 20 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 15 malicious IPs originating from Japan, positioning it as a notable contributor to global threat activity. 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

20.27.221.169 (280)20.210.188.132 (280)20.194.153.120 (280)104.46.236.39 (280)20.46.124.66 (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

💡 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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: