ABUSE.MOM
THREAT REPORT

IP Threat Report
20.151.114.166

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:06:09
First seen: 2026-02-25 23:00:08
Last seen: 2026-03-02 22:00:09
280

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHBURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 128Medium-risk: admin panels, config files+60
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 75 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 24 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 87 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 77 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 84 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 192Medium-risk: admin panels, config files+60
Burst: 74 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 40Medium-risk: admin panels, config files+60
Burst: 51 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 41Medium-risk: admin panels, config files+60
Burst: 25 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 52 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 38Medium-risk: admin panels, config files+60
Burst: 42 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 2Medium-risk: admin panels, config files+20
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 1500
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-02-25 23:00:08
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: 6 (+100), Danger medium hits: 128 (+60)
2026-03-02 22:00:09
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.151.114.166 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

🤖 Bot Detection

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

🌊 Traffic Flood Defense

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

🔎 Directory Scan Defense

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

20.151.114.166 has been assigned a threat score of 280/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

IP address 20.151.114.166 has been traced to Toronto, Canada, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 4 days, this IP generated 125 malicious requests, averaging approximately 31.3 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 106 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. 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 Canada

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

🏢 Same network: AS8075

20.151.111.128 (308)4.205.39.97 (283)20.63.36.125 (280)20.151.220.171 (280)20.104.114.39 (280)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: