ABUSE.MOM
THREAT REPORT

IP Threat Report
20.2.17.10

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 18:52:17
First seen: 2026-05-05 12:00:04
Last seen: 2026-05-05 12:00:04
155

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 26Medium-risk: admin panels, config files+60
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 27 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 155
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-05 12:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 26 (+60), Burst: 13 req / 2s (+35), Burst: 27 req / 10s (+35)
2026-05-05 12:00:04
Last malicious request observed
Total score reached: 155/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.2.17.10 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.2.17.10.

🔎 Directory Scan Defense

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (4)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
135UnknownLowService on port 135
445SMBCriticalSMB file sharing — high-risk for EternalBlue and ransomware
5985UnknownLowService on port 5985

⚠️ Network scanning reveals 1 dangerous service exposed on 20.2.17.10. SMB (445) exposure is associated with worm propagation and EternalBlue exploits. These services should not be publicly accessible without strict firewall rules.

KNOWN VULNERABILITIES (CVE) (1)
CVE IDLink
CVE-2020-0796NVD →

🔴 Security scanning identified 1 vulnerability entries on this host. Even a small number of CVEs can represent significant risk. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
microsoft:internet_information_services:10.0microsoft:internet_information_servicesmicrosoft:windowsmicrosoft:asp.net

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

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

Request FloodingPath Enumeration

📊 Threat Analysis

IP address 20.2.17.10 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. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. Our records show 101 malicious IPs originating from Hong Kong, positioning it as a significant contributor to global threat activity. A score of 155/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)40.83.92.30 (280)20.24.82.132 (280)23.100.90.148 (280)65.52.160.249 (280)View all →

🏢 Same network: AS8075

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

Security Intelligence

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

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

🔍 Check Any IP Address

Share this report: