ABUSE.MOM
THREAT REPORT

IP Threat Report
20.203.208.191

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-08-27 15:32:47
First seen: 2026-08-04 12:24:25
Last seen: 2026-08-16 01:04:20
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.203.208.191
Type
Hosting
Country
🇨🇭 Switzerland
City
Zurich
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (switzerlandnorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
13973
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 102/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 105/10sAbnormally fast request rate — automated scanning+35
Burst 106/10sAbnormally fast request rate — automated scanning+35
Burst 107/10sAbnormally fast request rate — automated scanning+35
Burst 108/10sAbnormally fast request rate — automated scanning+35
Burst 109/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 110/10sAbnormally fast request rate — automated scanning+35
Burst 111/10sAbnormally fast request rate — automated scanning+35
Burst 112/10sAbnormally fast request rate — automated scanning+35
Burst 113/10sAbnormally fast request rate — automated scanning+35
Burst 114/10sAbnormally fast request rate — automated scanning+35
Burst 115/10sAbnormally fast request rate — automated scanning+35
Burst 119/10sAbnormally fast request rate — automated scanning+35
Burst 120/10sAbnormally fast request rate — automated scanning+35
Burst 121/10sAbnormally fast request rate — automated scanning+35
Burst 123/10sAbnormally fast request rate — automated scanning+35
Burst 124/10sAbnormally fast request rate — automated scanning+35
Burst 125/10sAbnormally fast request rate — automated scanning+35
Burst 128/10sAbnormally fast request rate — automated scanning+35
Burst 130/10sAbnormally fast request rate — automated scanning+35
Burst 131/10sAbnormally fast request rate — automated scanning+35
Burst 132/10sAbnormally fast request rate — automated scanning+35
Burst 134/10sAbnormally fast request rate — automated scanning+35
Burst 136/10sAbnormally fast request rate — automated scanning+35
Burst 137/10sAbnormally fast request rate — automated scanning+35
Burst 138/10sAbnormally fast request rate — automated scanning+35
Burst 139/10sAbnormally fast request rate — automated scanning+35
Burst 140/10sAbnormally fast request rate — automated scanning+35
Burst 141/10sAbnormally fast request rate — automated scanning+35
Burst 142/10sAbnormally fast request rate — automated scanning+35
Burst 143/10sAbnormally fast request rate — automated scanning+35
Burst 144/10sAbnormally fast request rate — automated scanning+35
Burst 146/10sAbnormally fast request rate — automated scanning+35
Burst 147/10sAbnormally fast request rate — automated scanning+35
Burst 148/10sAbnormally fast request rate — automated scanning+35
Burst 151/10sAbnormally fast request rate — automated scanning+35
Burst 157/10sAbnormally fast request rate — automated scanning+35
Burst 166/10sAbnormally fast request rate — automated scanning+35
Burst 171/10sAbnormally fast request rate — automated scanning+35
Burst 172/10sAbnormally fast request rate — automated scanning+35
Burst 184/10sAbnormally fast request rate — automated scanning+35
Burst 186/10sAbnormally fast request rate — automated scanning+35
Burst 187/10sAbnormally fast request rate — automated scanning+35
Burst 191/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 26/2sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Burst 32/2sAbnormally fast request rate — automated scanning+35
Burst 33/2sAbnormally fast request rate — automated scanning+35
Burst 34/2sAbnormally fast request rate — automated scanning+35
Burst 35/10sAbnormally fast request rate — automated scanning+35
Burst 35/2sAbnormally fast request rate — automated scanning+35
Burst 36/2sAbnormally fast request rate — automated scanning+35
Burst 37/2sAbnormally fast request rate — automated scanning+35
Burst 38/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 40/2sAbnormally fast request rate — automated scanning+35
Burst 41/2sAbnormally fast request rate — automated scanning+35
Burst 42/2sAbnormally fast request rate — automated scanning+35
Burst 43/2sAbnormally fast request rate — automated scanning+35
Burst 44/2sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 47/2sAbnormally fast request rate — automated scanning+35
Burst 48/2sAbnormally fast request rate — automated scanning+35
Burst 49/2sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Burst 51/2sAbnormally fast request rate — automated scanning+35
Burst 52/2sAbnormally fast request rate — automated scanning+35
Burst 53/2sAbnormally fast request rate — automated scanning+35
Burst 54/2sAbnormally fast request rate — automated scanning+35
Burst 55/2sAbnormally fast request rate — automated scanning+35
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Burst 57/2sAbnormally fast request rate — automated scanning+35
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 59/2sAbnormally fast request rate — automated scanning+35
Burst 60/2sAbnormally fast request rate — automated scanning+35
Burst 61/2sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 62/2sAbnormally fast request rate — automated scanning+35
Burst 63/2sAbnormally fast request rate — automated scanning+35
Burst 64/10sAbnormally fast request rate — automated scanning+35
Burst 64/2sAbnormally fast request rate — automated scanning+35
Burst 65/10sAbnormally fast request rate — automated scanning+35
Burst 65/2sAbnormally fast request rate — automated scanning+35
Burst 66/2sAbnormally fast request rate — automated scanning+35
Burst 68/10sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Burst 74/10sAbnormally fast request rate — automated scanning+35
Burst 77/10sAbnormally fast request rate — automated scanning+35
Burst 78/10sAbnormally fast request rate — automated scanning+35
Burst 81/10sAbnormally fast request rate — automated scanning+35
Burst 82/10sAbnormally fast request rate — automated scanning+35
Burst 83/10sAbnormally fast request rate — automated scanning+35
Burst 84/10sAbnormally fast request rate — automated scanning+35
Burst 87/10sAbnormally fast request rate — automated scanning+35
Burst 88/10sAbnormally fast request rate — automated scanning+35
Burst 91/10sAbnormally fast request rate — automated scanning+35
Burst 92/10sAbnormally fast request rate — automated scanning+35
Burst 93/10sAbnormally fast request rate — automated scanning+35
Burst 94/10sAbnormally fast request rate — automated scanning+35
Burst 95/10sAbnormally fast request rate — automated scanning+35
Burst 96/10sAbnormally fast request rate — automated scanning+35
Burst 97/10sAbnormally fast request rate — automated scanning+35
Burst 98/10sAbnormally fast request rate — automated scanning+35
Burst 99/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 112Medium-risk: admin panels, config files+60
Danger medium hits: 113Medium-risk: admin panels, config files+60
Danger medium hits: 114Medium-risk: admin panels, config files+60
Danger medium hits: 115Medium-risk: admin panels, config files+60
Danger medium hits: 117Medium-risk: admin panels, config files+60
Danger medium hits: 126Medium-risk: admin panels, config files+60
Danger medium hits: 130Medium-risk: admin panels, config files+60
Danger medium hits: 134Medium-risk: admin panels, config files+60
Danger medium hits: 135Medium-risk: admin panels, config files+60
Danger medium hits: 141Medium-risk: admin panels, config files+60
Danger medium hits: 144Medium-risk: admin panels, config files+60
Danger medium hits: 150Medium-risk: admin panels, config files+60
Danger medium hits: 152Medium-risk: admin panels, config files+60
Danger medium hits: 153Medium-risk: admin panels, config files+60
Danger medium hits: 163Medium-risk: admin panels, config files+60
Danger medium hits: 170Medium-risk: admin panels, config files+60
Danger medium hits: 171Medium-risk: admin panels, config files+60
Danger medium hits: 174Medium-risk: admin panels, config files+60
Danger medium hits: 188Medium-risk: admin panels, config files+60
Danger medium hits: 189Medium-risk: admin panels, config files+60
Danger medium hits: 191Medium-risk: admin panels, config files+60
Danger medium hits: 192Medium-risk: admin panels, config files+60
Danger medium hits: 201Medium-risk: admin panels, config files+60
Danger medium hits: 203Medium-risk: admin panels, config files+60
Danger medium hits: 204Medium-risk: admin panels, config files+60
Danger medium hits: 210Medium-risk: admin panels, config files+60
Danger medium hits: 211Medium-risk: admin panels, config files+60
Danger medium hits: 224Medium-risk: admin panels, config files+60
Danger medium hits: 226Medium-risk: admin panels, config files+60
Danger medium hits: 228Medium-risk: admin panels, config files+60
Danger medium hits: 229Medium-risk: admin panels, config files+60
Danger medium hits: 232Medium-risk: admin panels, config files+60
Danger medium hits: 261Medium-risk: admin panels, config files+60
Danger medium hits: 264Medium-risk: admin panels, config files+60
Danger medium hits: 266Medium-risk: admin panels, config files+60
Danger medium hits: 268Medium-risk: admin panels, config files+60
Danger medium hits: 284Medium-risk: admin panels, config files+60
Danger medium hits: 288Medium-risk: admin panels, config files+60
Danger medium hits: 302Medium-risk: admin panels, config files+60
Danger medium hits: 306Medium-risk: admin panels, config files+60
Danger medium hits: 308Medium-risk: admin panels, config files+60
Danger medium hits: 318Medium-risk: admin panels, config files+60
Danger medium hits: 322Medium-risk: admin panels, config files+60
Danger medium hits: 324Medium-risk: admin panels, config files+60
Danger medium hits: 333Medium-risk: admin panels, config files+60
Danger medium hits: 336Medium-risk: admin panels, config files+60
Danger medium hits: 340Medium-risk: admin panels, config files+60
Danger medium hits: 380Medium-risk: admin panels, config files+60
Danger medium hits: 402Medium-risk: admin panels, config files+60
Danger medium hits: 410Medium-risk: admin panels, config files+60
Danger medium hits: 431Medium-risk: admin panels, config files+60
Danger medium hits: 432Medium-risk: admin panels, config files+60
Danger medium hits: 57Medium-risk: admin panels, config files+60
Danger medium hits: 67Medium-risk: admin panels, config files+60
Danger medium hits: 74Medium-risk: admin panels, config files+60
Danger medium hits: 77Medium-risk: admin panels, config files+60
Danger medium hits: 78Medium-risk: admin panels, config files+60
Danger medium hits: 79Medium-risk: admin panels, config files+60
Danger medium hits: 94Medium-risk: admin panels, config files+60
Danger medium hits: 95Medium-risk: admin panels, config files+60
Danger medium hits: 96Medium-risk: admin panels, config files+60
Danger medium hits: 97Medium-risk: admin panels, config files+60
Danger medium hits: 98Medium-risk: admin panels, config files+60
Danger medium hits: 99Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 8730
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-04 12:24:25
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 102/10s (+35)
2026-08-16 01:04:20
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.208.191 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.208.0/24
  • 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.203.208.191: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

IP 20.203.208.191 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

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

07

Neighbors in 20.203.208.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.

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

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

10

Threat Analysis

20.203.208.191 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

20.203.208.191 is registered in Zurich, Switzerland, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 13,973 malicious requests from this address across a 11-day span, reflecting a sustained attack cadence of ~1270.3 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 103 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

34.65.117.95 (298)34.65.167.1 (288)20.203.149.15 (280)20.250.28.140 (280)20.250.9.235 (280)View all →

🏢 Same network: AS8075

51.103.130.248 (280)20.203.205.107 (280)20.203.129.163 (280)20.203.209.227 (280)51.107.70.126 (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.

💡 DNS Amplification Attack Mechanics

DNS amplification exploits open resolvers to reflect and amplify traffic toward victims. A small query triggers a large response directed at the spoofed source IP, achieving amplification factors of 50x or more, overwhelming target bandwidth.

🔍 Check Any IP Address

Share this report: