ABUSE.MOM
THREAT REPORT

IP Threat Report
20.104.253.228

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:41:18
First seen: 2026-04-29 00:00:10
Last seen: 2026-04-29 00:00:10
160

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
Σ = 160
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-29 00:00:10
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 4 (+100), Danger medium hits: 6 (+60)
2026-04-29 00:00:10
Last malicious request observed
Total score reached: 160/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.253.228 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

⚙️ Defensive Recommendations

Block 20.104.253.228 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

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

📊 Threat Analysis

20.104.253.228 is registered in Toronto, Canada, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Canada currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 160/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

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

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

🔍 Check Any IP Address

Share this report: