ABUSE.MOM
THREAT REPORT

IP Threat Report
65.52.165.203

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 04:05:41
First seen: 2026-06-28 23:33:27
Last seen: 2026-07-05 04:02:12
245

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_SUS
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 49/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 297Medium-risk: admin panels, config files+60
Danger medium hits: 72Medium-risk: admin panels, config files+60
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 380
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-06-28 23:33:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/2s (+35), Burst 49/10s (+35), Danger medium hits: 297 (+60)
2026-07-05 04:02:12
Last malicious request observed
Total score reached: 245/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 65.52.165.203 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 65.52.165.203.

🤖 Bot Detection

Address UA spoofing from 65.52.165.203: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

65.52.165.203 has been assigned a threat score of 245/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 FloodingUser-Agent Anomaly

📊 Threat Analysis

65.52.165.203 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 6 days in our monitoring system, producing 714 flagged requests at a rate of ~119/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Hong Kong currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 245/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.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.

💡 Submarine Cable and Internet Exchange Points

Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.

🔍 Check Any IP Address

Share this report: