ABUSE.MOM
THREAT REPORT

IP Threat Report
20.205.120.43

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:18:41
First seen: 2026-02-17 17:25:06
Last seen: 2026-03-16 02:00: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: 98.

DANGER_PATHRATIO_404BURSTIMPORT
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 24Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 25 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 15 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 22 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 17 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 16 req / 10sAbnormally fast request rate — automated scanning+35
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Danger medium hits: 25Medium-risk: admin panels, config files+60
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 38 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 35 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 40Medium-risk: admin panels, config files+60
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 49 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 47 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 48High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 61Medium-risk: admin panels, config files+60
Burst: 54 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 44 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 16 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 55 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 60High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 74Medium-risk: admin panels, config files+60
Burst: 53 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 89Medium-risk: admin panels, config files+60
Danger strong hits: 34High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 77Medium-risk: admin panels, config files+60
Burst: 48 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 39Medium-risk: admin panels, config files+60
Burst: 40 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 46 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 41Medium-risk: admin panels, config files+60
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 60Medium-risk: admin panels, config files+60
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 34 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 49High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 70Medium-risk: admin panels, config files+60
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 28Medium-risk: admin panels, config files+60
Burst: 37 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 54Medium-risk: admin panels, config files+60
Burst: 43 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 16Medium-risk: admin panels, config files+60
Burst: 18 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 35Medium-risk: admin panels, config files+60
Burst: 33 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Σ = 3335
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
Danger strong hits: 10 (+100), Danger medium hits: 24 (+60), 404 ratio >= 60% (+25)
2026-03-16 02:00: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.120.43 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.205.120.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 20.205.120.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.205.120.43 has been assigned a threat score of 255/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:

Path EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 20.205.120.43 to malicious activity originating from Hong Kong, Hong Kong, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 26 days, this IP generated 98 malicious requests, averaging approximately 3.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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 101 malicious IPs originating from Hong Kong, positioning it as a significant contributor to global threat activity. 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.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

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: