ABUSE.MOM
THREAT REPORT

IP Threat Report
89.251.0.80

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 14:37:32
First seen: 2026-06-06 15:59:02
Last seen: 2026-07-05 14:35:49
100

⛔ Verdict: BLOCK

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

METHODRATIO_404REFERERspam
01

Geolocation & Classification

IP Address
89.251.0.80
Type
Unknown
Country
🇨🇦 Canada
City
Toronto
ISP
Orion Network Limited
Organization
Orion Network Limited
Autonomous System
Unknown
Hit Count
76
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
spam:no_js_checkSpam/malware keywords in request content+0
Σ = 43
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-06-06 15:59:02
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), DDoS / Flood, Foreign referer (+10)
2026-07-05 14:35:49
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 89.251.0.80 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
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 89.251.0.80: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

📧 Spam Protection

Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.

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

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

10

Threat Analysis

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

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 89.251.0.80 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. Our sensors captured 76 malicious requests from this address across a 28-day span, reflecting a sustained attack cadence of ~2.7 requests per day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 149 flagged addresses, Canada represents a significant presence in our threat database. At 100/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇨🇦 Top threats from Canada

20.151.179.130 (308)20.151.111.128 (308)45.91.23.64 (305)147.15.149.40 (300)148.116.72.171 (300)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.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: