ABUSE.MOM
THREAT REPORT

IP Threat Report
20.194.96.114

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 18:29:55
First seen: 2026-10-03 08:14:32
Last seen: 2026-10-11 01:06: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: 4092.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERERUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
20.194.96.114
Type
Hosting
Country
🇰🇷 South Korea
City
Seoul
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (koreacentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
4092
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 11/2sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 18/10sAbnormally fast request rate — automated scanning+35
Burst 35/10sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 37/10sAbnormally fast request rate — automated scanning+35
Burst 38/10sAbnormally fast request rate — automated scanning+35
Burst 39/10sAbnormally fast request rate — automated scanning+35
Burst 40/10sAbnormally fast request rate — automated scanning+35
Burst 41/10sAbnormally fast request rate — automated scanning+35
Burst 42/10sAbnormally fast request rate — automated scanning+35
Burst 43/10sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 102Medium-risk: admin panels, config files+60
Danger medium hits: 103Medium-risk: admin panels, config files+60
Danger medium hits: 104Medium-risk: admin panels, config files+60
Danger medium hits: 117Medium-risk: admin panels, config files+60
Danger medium hits: 124Medium-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: 133Medium-risk: admin panels, config files+60
Danger medium hits: 135Medium-risk: admin panels, config files+60
Danger medium hits: 136Medium-risk: admin panels, config files+60
Danger medium hits: 146Medium-risk: admin panels, config files+60
Danger medium hits: 148Medium-risk: admin panels, config files+60
Danger medium hits: 151Medium-risk: admin panels, config files+60
Danger medium hits: 162Medium-risk: admin panels, config files+60
Danger medium hits: 185Medium-risk: admin panels, config files+60
Danger medium hits: 194Medium-risk: admin panels, config files+60
Danger medium hits: 198Medium-risk: admin panels, config files+60
Danger medium hits: 221Medium-risk: admin panels, config files+60
Danger medium hits: 228Medium-risk: admin panels, config files+60
Danger medium hits: 252Medium-risk: admin panels, config files+60
Danger medium hits: 266Medium-risk: admin panels, config files+60
Danger medium hits: 272Medium-risk: admin panels, config files+60
Danger medium hits: 288Medium-risk: admin panels, config files+60
Danger medium hits: 289Medium-risk: admin panels, config files+60
Danger medium hits: 302Medium-risk: admin panels, config files+60
Danger medium hits: 308Medium-risk: admin panels, config files+60
Danger medium hits: 33Medium-risk: admin panels, config files+60
Danger medium hits: 330Medium-risk: admin panels, config files+60
Danger medium hits: 350Medium-risk: admin panels, config files+60
Danger medium hits: 351Medium-risk: admin panels, config files+60
Danger medium hits: 388Medium-risk: admin panels, config files+60
Danger medium hits: 462Medium-risk: admin panels, config files+60
Danger medium hits: 47Medium-risk: admin panels, config files+60
Danger medium hits: 504Medium-risk: admin panels, config files+60
Danger medium hits: 566Medium-risk: admin panels, config files+60
Danger medium hits: 62Medium-risk: admin panels, config files+60
Danger medium hits: 68Medium-risk: admin panels, config files+60
Danger medium hits: 705Medium-risk: admin panels, config files+60
Danger medium hits: 90Medium-risk: admin panels, config files+60
Danger medium hits: 94Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 106High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 132High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 149High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 15High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 21High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 29High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 31High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 34High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 35High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 38High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 41High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 42High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 54High-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: 77High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 89High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 5500
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-10-03 08:14:32
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 11/2s (+35)
2026-10-11 01:06: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 · 🇰🇷 South Korea

We have detected 1853 malicious IPs from this autonomous system.

View all IPs from AS8075 →
06

Recommendations

Actions taken & recommended

  • IP 20.194.96.114 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.194.96.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.194.96.114: 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.194.96.114.

🤖 Bot Detection

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

07

Neighbors in 20.194.96.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
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

20.194.96.114 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:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 20.194.96.114, geolocated to Seoul, South Korea, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Our sensors captured 4,092 malicious requests from this address across a 7-day span, reflecting a sustained attack cadence of ~584.6 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. South Korea currently accounts for 601 blocked IPs in our database, making it a major source of malicious traffic. With a threat score of 280/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 South Korea

220.118.151.107 (310)175.197.250.36 (310)58.127.77.173 (310)34.64.167.219 (293)34.64.98.171 (288)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)20.92.77.159 (310)20.210.128.125 (310)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.

💡 Satellite Internet Security

Satellite internet introduces unique security challenges including high latency that affects real-time threat detection, shared bandwidth that enables traffic sniffing, and coverage areas that cross multiple jurisdictions complicating legal response.

🔍 Check Any IP Address

Share this report: