ABUSE.MOM
THREAT REPORT

IP Threat Report
20.2.140.73

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 19:09:57
First seen: 2026-05-15 06:00:05
Last seen: 2026-05-15 06:00:05
145

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 145
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-15 06:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 2 (+50), Burst: 11 req / 2s (+35)
2026-05-15 06:00:05
Last malicious request observed
Total score reached: 145/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.140.73 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

🤖 User-Agent Anomaly Defense

IP 20.2.140.73 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Traffic Flood Defense

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

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

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

10

Threat Analysis

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

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

20.2.140.73 is registered in Hong Kong, Hong Kong, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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 (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Hong Kong currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 145/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 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

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Log Correlation and SIEM Integration

Correlating logs across web servers, firewalls, DNS, and authentication systems reveals attack patterns invisible in individual log sources. Modern SIEM platforms use statistical analysis to connect related events across time and systems.

🔍 Check Any IP Address

Share this report: