ABUSE.MOM
THREAT REPORT

IP Threat Report
20.78.145.252

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:01:03
First seen: 2026-03-09 02:00:06
Last seen: 2026-03-26 08:00:08
255

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 28Medium-risk: admin panels, config files+60
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 37 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 26Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 32 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 51Medium-risk: admin panels, config files+60
Burst: 42 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 40 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 38 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 41Medium-risk: admin panels, config files+60
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 33Medium-risk: admin panels, config files+60
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 42Medium-risk: admin panels, config files+60
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 204Medium-risk: admin panels, config files+60
Danger strong hits: 27High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 207Medium-risk: admin panels, config files+60
Burst: 41 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 20Medium-risk: admin panels, config files+60
Burst: 39 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 43 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 86Medium-risk: admin panels, config files+60
Danger medium hits: 121Medium-risk: admin panels, config files+60
Danger medium hits: 22Medium-risk: admin panels, config files+60
Burst: 24 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 21Medium-risk: admin panels, config files+60
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 23Medium-risk: admin panels, config files+60
Σ = 2250
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-09 02:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 13 (+100), Danger medium hits: 28 (+60), Burst: 12 req / 2s (+35)
2026-03-26 08:00:08
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.78.145.252 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.78.145.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

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

🔎 Path Enumeration Protection

Block scanning from 20.78.145.252: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 20.78.145.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.78.145.252 has been assigned a threat score of 255/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 20.78.145.252 to malicious activity originating from Osaka, Japan, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Our sensors captured 116 malicious requests from this address across a 17-day span, reflecting a sustained attack cadence of ~6.8 requests per 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. Two attack patterns were identified (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Japan currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 255/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

🇯🇵 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

20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)20.194.153.120 (280)104.46.236.39 (280)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Threat Intelligence Sharing Frameworks

Standards like STIX/TAXII, MISP, and OpenIOC enable automated sharing of threat intelligence between organizations. Collective defense through shared indicators, tactics, and procedures strengthens the entire security community against common threats.

🔍 Check Any IP Address

Share this report: