ABUSE.MOM
THREAT REPORT

IP Threat Report
20.203.162.164

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:05:30
First seen: 2026-04-25 11:00:06
Last seen: 2026-04-25 20:00:06
280

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHRATIO_404REDIRECT_PROBEBURST
01

Geolocation & Classification

IP Address
20.203.162.164
Type
Hosting
Country
🇨🇭 Switzerland
City
Zurich
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (switzerlandnorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
8
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 72High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 609Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 37 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 119 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 49High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 305Medium-risk: admin panels, config files+60
Burst: 34 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 104 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 42 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 137 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 128 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 311Medium-risk: admin panels, config files+60
Burst: 46 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 142 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 67High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 464Medium-risk: admin panels, config files+60
Burst: 38 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 130 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
Burst: 35 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 121 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 308Medium-risk: admin panels, config files+60
Burst: 45 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 1240
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-04-25 11:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 72 (+100), Danger medium hits: 609 (+60)
2026-04-25 20:00:06
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 · 🇨🇭 Switzerland
06

Recommendations

Actions taken & recommended

  • IP 20.203.162.164 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.203.162.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

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

🔎 Directory Scan Defense

IP 20.203.162.164 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.203.162.164.

07

Neighbors in 20.203.162.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
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.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.203.162.164 has been assigned a threat score of 280/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:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

The address 20.203.162.164 originates from Zurich, Switzerland, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 1-day observation window, we recorded 8 hostile requests from this IP — roughly 8 per day on average. 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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 102 flagged addresses, Switzerland 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 Switzerland

51.107.69.151 (280)20.250.10.152 (280)20.203.180.135 (280)20.203.136.132 (280)20.203.129.217 (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

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Threat Score Calculation Methods

Threat scoring combines multiple signals — request patterns, known signatures, IP reputation, geographic risk, and behavioral analysis — into a single actionable metric. Weighted scoring models allow tuning sensitivity to balance security with usability.

🔍 Check Any IP Address

Share this report: