ABUSE.MOM
THREAT REPORT

IP Threat Report
20.205.14.113

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 06:33:32
First seen: 2026-07-03 14:22:12
Last seen: 2026-07-05 04:03:07
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
20.205.14.113
Type
Hosting
Country
🇭🇰 Hong Kong
City
Hong Kong
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (eastasia)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
277
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 48/10sAbnormally fast request rate — automated scanning+35
Burst 49/10sAbnormally fast request rate — automated scanning+35
Burst 50/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 103Medium-risk: admin panels, config files+60
Danger strong hits: 47High-risk paths: shells, RCE vectors, exploits+100
Σ = 325
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-03 14:22:12
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 14/2s (+35), Burst 48/10s (+35)
2026-07-05 04:03:07
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 · 🇭🇰 Hong Kong
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

IP 20.205.14.113 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.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

20.205.14.113 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:

Path EnumerationRequest Flooding

📊 Threat Analysis

IP address 20.205.14.113 has been traced to Hong Kong, Hong Kong, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 277 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~277 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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Hong Kong currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. A score of 255/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 Hong Kong

20.24.198.93 (280)20.24.82.132 (280)20.187.125.76 (280)20.187.67.15 (280)20.205.115.105 (280)View all →

🏢 Same network: AS8075

20.226.81.88 (280)20.48.26.146 (280)52.237.113.70 (280)104.208.65.18 (280)20.226.50.160 (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.

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: