ABUSE.MOM
THREAT REPORT

IP Threat Report
20.104.50.116

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:53:53
First seen: 2026-07-02 14:17:19
Last seen: 2026-07-12 00:57:59
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.104.50.116
Type
Hosting
Country
🇨🇦 Canada
City
Toronto
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (canadacentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
12340
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 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 18/10sAbnormally fast request rate — automated scanning+35
Burst 18/2sAbnormally fast request rate — automated scanning+35
Burst 19/2sAbnormally fast request rate — automated scanning+35
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 21/2sAbnormally 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 34/10sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 41/10sAbnormally fast request rate — automated scanning+35
Burst 44/10sAbnormally fast request rate — automated scanning+35
Burst 45/10sAbnormally fast request rate — automated scanning+35
Burst 47/10sAbnormally fast request rate — automated scanning+35
Burst 48/10sAbnormally fast request rate — automated scanning+35
Burst 49/10sAbnormally fast request rate — automated scanning+35
Burst 50/10sAbnormally fast request rate — automated scanning+35
Burst 52/10sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 56/10sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Burst 58/10sAbnormally fast request rate — automated scanning+35
Burst 59/10sAbnormally fast request rate — automated scanning+35
Burst 60/10sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 64/10sAbnormally fast request rate — automated scanning+35
Burst 65/10sAbnormally fast request rate — automated scanning+35
Burst 66/10sAbnormally fast request rate — automated scanning+35
Burst 67/10sAbnormally fast request rate — automated scanning+35
Burst 68/10sAbnormally fast request rate — automated scanning+35
Burst 69/10sAbnormally fast request rate — automated scanning+35
Burst 70/10sAbnormally fast request rate — automated scanning+35
Burst 71/10sAbnormally fast request rate — automated scanning+35
Burst 72/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 75/10sAbnormally fast request rate — automated scanning+35
Burst 76/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 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 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 85/10sAbnormally fast request rate — automated scanning+35
Burst 86/10sAbnormally fast request rate — automated scanning+35
Burst 87/10sAbnormally 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: 104Medium-risk: admin panels, config files+60
Danger medium hits: 105Medium-risk: admin panels, config files+60
Danger medium hits: 120Medium-risk: admin panels, config files+60
Danger medium hits: 126Medium-risk: admin panels, config files+60
Danger medium hits: 132Medium-risk: admin panels, config files+60
Danger medium hits: 136Medium-risk: admin panels, config files+60
Danger medium hits: 137Medium-risk: admin panels, config files+60
Danger medium hits: 139Medium-risk: admin panels, config files+60
Danger medium hits: 148Medium-risk: admin panels, config files+60
Danger medium hits: 150Medium-risk: admin panels, config files+60
Danger medium hits: 158Medium-risk: admin panels, config files+60
Danger medium hits: 179Medium-risk: admin panels, config files+60
Danger medium hits: 18Medium-risk: admin panels, config files+60
Danger medium hits: 182Medium-risk: admin panels, config files+60
Danger medium hits: 183Medium-risk: admin panels, config files+60
Danger medium hits: 184Medium-risk: admin panels, config files+60
Danger medium hits: 187Medium-risk: admin panels, config files+60
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 200Medium-risk: admin panels, config files+60
Danger medium hits: 201Medium-risk: admin panels, config files+60
Danger medium hits: 202Medium-risk: admin panels, config files+60
Danger medium hits: 204Medium-risk: admin panels, config files+60
Danger medium hits: 220Medium-risk: admin panels, config files+60
Danger medium hits: 222Medium-risk: admin panels, config files+60
Danger medium hits: 230Medium-risk: admin panels, config files+60
Danger medium hits: 232Medium-risk: admin panels, config files+60
Danger medium hits: 273Medium-risk: admin panels, config files+60
Danger medium hits: 275Medium-risk: admin panels, config files+60
Danger medium hits: 276Medium-risk: admin panels, config files+60
Danger medium hits: 279Medium-risk: admin panels, config files+60
Danger medium hits: 28Medium-risk: admin panels, config files+60
Danger medium hits: 280Medium-risk: admin panels, config files+60
Danger medium hits: 290Medium-risk: admin panels, config files+60
Danger medium hits: 291Medium-risk: admin panels, config files+60
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger medium hits: 30Medium-risk: admin panels, config files+60
Danger medium hits: 317Medium-risk: admin panels, config files+60
Danger medium hits: 324Medium-risk: admin panels, config files+60
Danger medium hits: 327Medium-risk: admin panels, config files+60
Danger medium hits: 34Medium-risk: admin panels, config files+60
Danger medium hits: 348Medium-risk: admin panels, config files+60
Danger medium hits: 356Medium-risk: admin panels, config files+60
Danger medium hits: 36Medium-risk: admin panels, config files+60
Danger medium hits: 374Medium-risk: admin panels, config files+60
Danger medium hits: 38Medium-risk: admin panels, config files+60
Danger medium hits: 384Medium-risk: admin panels, config files+60
Danger medium hits: 387Medium-risk: admin panels, config files+60
Danger medium hits: 419Medium-risk: admin panels, config files+60
Danger medium hits: 46Medium-risk: admin panels, config files+60
Danger medium hits: 475Medium-risk: admin panels, config files+60
Danger medium hits: 48Medium-risk: admin panels, config files+60
Danger medium hits: 491Medium-risk: admin panels, config files+60
Danger medium hits: 5Medium-risk: admin panels, config files+50
Danger medium hits: 50Medium-risk: admin panels, config files+60
Danger medium hits: 521Medium-risk: admin panels, config files+60
Danger medium hits: 53Medium-risk: admin panels, config files+60
Danger medium hits: 54Medium-risk: admin panels, config files+60
Danger medium hits: 579Medium-risk: admin panels, config files+60
Danger medium hits: 599Medium-risk: admin panels, config files+60
Danger medium hits: 60Medium-risk: admin panels, config files+60
Danger medium hits: 68Medium-risk: admin panels, config files+60
Danger medium hits: 71Medium-risk: admin panels, config files+60
Danger medium hits: 72Medium-risk: admin panels, config files+60
Danger medium hits: 75Medium-risk: admin panels, config files+60
Danger medium hits: 79Medium-risk: admin panels, config files+60
Danger medium hits: 80Medium-risk: admin panels, config files+60
Danger medium hits: 89Medium-risk: admin panels, config files+60
Danger medium hits: 9Medium-risk: admin panels, config files+60
Danger medium hits: 91Medium-risk: admin panels, config files+60
Danger medium hits: 92Medium-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: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-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: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 20High-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: 26High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 27High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 33High-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: 36High-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: 43High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 48High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 49High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 60High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 68High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 72High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 80High-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
Σ = 9675
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-07-02 14:17:19
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 14/2s (+35)
2026-07-12 00:57:59
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 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 20.104.50.116 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.104.50.116: 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.104.50.116.

🤖 Bot Detection

Address UA spoofing from 20.104.50.116: 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
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net

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

10

Threat Analysis

20.104.50.116 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

Network traffic from 20.104.50.116, located in Toronto, Canada, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. The address has been active for 9 days in our monitoring system, producing 12,340 flagged requests at a rate of ~1371.1/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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 103 flagged addresses, Canada represents a significant presence in our threat database. 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 Canada

20.151.179.130 (308)20.151.111.128 (308)45.91.23.64 (305)45.91.23.164 (305)147.15.149.40 (300)View all →

🏢 Same network: AS8075

20.220.14.153 (280)20.104.74.38 (280)20.63.86.26 (280)20.220.62.118 (280)20.220.148.251 (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.

💡 Automated Incident Response

Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.

🔍 Check Any IP Address

Share this report: