ABUSE.MOM
THREAT REPORT

IP Threat Report
20.75.92.165

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-08-30 01:26:13
First seen: 2026-08-18 00:30:29
Last seen: 2026-08-30 01:03:49
280

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHMETHODRATIO_404REDIRECT_PROBEREFERERUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
20.75.92.165
Type
Hosting
Country
🇺🇸 United States
City
Boydton
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (eastus2)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
1651
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 21/10sAbnormally fast request rate — automated scanning+35
Burst 22/2sAbnormally fast request rate — automated scanning+35
Burst 23/2sAbnormally fast request rate — automated scanning+35
Burst 24/2sAbnormally fast request rate — automated scanning+35
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Burst 70/10sAbnormally fast request rate — automated scanning+35
Burst 75/10sAbnormally fast request rate — automated scanning+35
Burst 79/10sAbnormally fast request rate — automated scanning+35
Burst 80/10sAbnormally fast request rate — automated scanning+35
Burst 81/10sAbnormally fast request rate — automated scanning+35
Burst 84/10sAbnormally fast request rate — automated scanning+35
Burst 86/10sAbnormally fast request rate — automated scanning+35
Burst 88/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 13Medium-risk: admin panels, config files+60
Danger medium hits: 134Medium-risk: admin panels, config files+60
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 224Medium-risk: admin panels, config files+60
Danger medium hits: 261Medium-risk: admin panels, config files+60
Danger medium hits: 262Medium-risk: admin panels, config files+60
Danger medium hits: 268Medium-risk: admin panels, config files+60
Danger medium hits: 300Medium-risk: admin panels, config files+60
Danger medium hits: 451Medium-risk: admin panels, config files+60
Danger medium hits: 65Medium-risk: admin panels, config files+60
Danger medium hits: 8Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 104High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 15High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 44High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 52High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 54High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 60High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 78High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 2323
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-08-18 00:30:29
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 13/2s (+35)
2026-08-30 01:03:49
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 20.75.92.165 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

🔎 Path Enumeration Protection

Block scanning from 20.75.92.165: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

20.75.92.165 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 20.75.92.165 originates from Boydton, United States, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 12 days in our monitoring system, producing 1,651 flagged requests at a rate of ~137.6/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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 108 flagged addresses, United States represents a significant presence in our threat database. A score of 280/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 United States

104.28.246.115 (350)104.28.214.122 (350)34.187.158.4 (340)34.186.187.208 (340)104.28.214.116 (340)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.220.203.117 (280)20.79.30.30 (280)20.91.139.111 (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.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: