ABUSE.MOM
THREAT REPORT

IP Threat Report
20.220.223.1

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:12:39
First seen: 2026-03-22 19:00:05
Last seen: 2026-03-23 00:00:10
245

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHBURST
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 57Medium-risk: admin panels, config files+60
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 54 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 68High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 241Medium-risk: admin panels, config files+60
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 75 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 100High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 442Medium-risk: admin panels, config files+60
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 77 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 78High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 298Medium-risk: admin panels, config files+60
Burst: 73 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 104High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 448Medium-risk: admin panels, config files+60
Burst: 74 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 84 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 156High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 596Medium-risk: admin panels, config files+60
Burst: 66 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 48 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 170 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 1430
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-22 19:00:05
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: 10 (+100), Danger medium hits: 57 (+60)
2026-03-23 00:00:10
Last malicious request observed
Total score reached: 245/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.220.223.1 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.220.223.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 20.220.223.1 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.220.223.1.

07

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

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

10

Threat Analysis

20.220.223.1 has been assigned a threat score of 245/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:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

The address 20.220.223.1 originates from Toronto, Canada, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 11 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~11 requests per 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. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 102 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. A score of 245/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

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 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.

💡 False Positive Management

False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.

🔍 Check Any IP Address

Share this report: