ABUSE.MOM
THREAT REPORT

IP Threat Report
20.220.148.76

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 06:13:40
First seen: 2026-05-18 23:51:55
Last seen: 2026-05-22 05:55:18
230

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 22/2sAbnormally fast request rate — automated scanning+35
Burst 68/10sAbnormally fast request rate — automated scanning+35
Burst 70/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
Danger medium hits: 90Medium-risk: admin panels, config files+60
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Σ = 370
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-05-18 23:51:55
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 21/2s (+35), Burst 22/2s (+35), Burst 68/10s (+35)
2026-05-22 05:55:18
Last malicious request observed
Total score reached: 230/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.148.76 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.148.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 20.220.148.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
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Request Flooding

📊 Threat Analysis

20.220.148.76 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 3 days in our monitoring system, producing 433 flagged requests at a rate of ~144.3/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Canada currently accounts for 103 blocked IPs in our database, making it a significant source of malicious traffic. A score of 230/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

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

💡 GDPR and Threat Intelligence

Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.

🔍 Check Any IP Address

Share this report: