ABUSE.MOM
THREAT REPORT

IP Threat Report
89.251.0.6

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:55:13
First seen: 2026-05-26 04:09:14
Last seen: 2026-05-30 07:17:28
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
89.251.0.6
Type
VPN
Country
🇨🇦 Canada
City
Toronto
ISP
Orion Network Limited
Organization
VPN Consumer Toronto, Canada
Autonomous System
AS41564 Orion Network Limited
Hit Count
152
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 49Medium-risk: admin panels, config files+60
Danger strong hits: 126High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 46High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 425
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-26 04:09:14
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 16/2s (+35), Burst 17/2s (+35), Burst 54/10s (+35)
2026-05-30 07:17:28
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

Orion Network Limited
AS41564 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 89.251.0.6 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 89.251.0.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 89.251.0.6.

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 89.251.0.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
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

89.251.0.6 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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 89.251.0.6 has been traced to Toronto, Canada, operating on the network of Orion Network Limited. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 4-day observation window, we recorded 152 hostile requests from this IP — roughly 38 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 176 flagged addresses, Canada represents a significant presence in our threat database. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

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: AS41564

89.251.0.24 (295)89.251.0.128 (295)89.251.0.26 (280)89.251.0.123 (270)89.251.0.110 (255)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.

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

🔍 Check Any IP Address

Share this report: