ABUSE.MOM
THREAT REPORT

IP Threat Report
20.104.192.115

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-20 19:55:30
First seen: 2026-03-19 19:00:04
Last seen: 2026-03-20 07:00:05
255

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404BURST
01

Geolocation & Classification

IP Address
20.104.192.115
Type
Hosting
Country
🇨🇦 Canada
City
Toronto
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (canadacentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
57
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 39Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 19 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 52 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 38High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 78Medium-risk: admin panels, config files+60
Burst: 32 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 82 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 47Medium-risk: admin panels, config files+60
Burst: 57 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 94Medium-risk: admin panels, config files+60
Burst: 34 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 100 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 28 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 52Medium-risk: admin panels, config files+60
Burst: 66 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 46Medium-risk: admin panels, config files+60
Burst: 65 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 46High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 92Medium-risk: admin panels, config files+60
Burst: 122 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 63 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 1675
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-03-19 19:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 19 (+100), Danger medium hits: 39 (+60), 404 ratio >= 60% (+25)
2026-03-20 07:00:05
Last malicious request observed
Total score reached: 255/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.192.115 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

🔎 Directory Scan Defense

IP 20.104.192.115 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

20.104.192.115 has been assigned a threat score of 255/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 Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 20.104.192.115 to malicious activity originating from Toronto, Canada, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 57 malicious requests, averaging approximately 57 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 101 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. A score of 255/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 Canada

45.91.23.64 (305)147.15.149.40 (300)148.116.72.171 (300)89.251.0.24 (295)89.251.0.128 (295)View all →

🏢 Same network: AS8075

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

🔍 Check Any IP Address

Share this report: