ABUSE.MOM
THREAT REPORT

IP Threat Report
20.205.116.138

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:01:07
First seen: 2026-05-18 15:00:05
Last seen: 2026-05-24 09:52:16
230

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 46/10sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 46 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Σ = 400
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-05-18 15:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/2s (+35), Burst 46/10s (+35), Burst: 14 req / 2s (+35)
2026-05-24 09:52:16
Last malicious request observed
Total score reached: 230/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.116.138 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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

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

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

10

Threat Analysis

20.205.116.138 has been assigned a threat score of 230/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 Flooding

📊 Threat Analysis

IP address 20.205.116.138 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. During its 5-day observation window, we recorded 219 hostile requests from this IP — roughly 43.8 per day on average. 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 101 malicious IPs originating from Hong Kong, positioning it as a significant contributor to global threat activity. A score of 230/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.205.115.105 (280)20.24.82.132 (280)23.100.90.148 (280)65.52.160.249 (280)20.187.125.76 (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

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

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: