ABUSE.MOM
THREAT REPORT

IP Threat Report
139.28.218.146

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 04:50:53
First seen: 2026-05-11 11:00:06
Last seen: 2026-05-11 11:00:06
60

⛔ Verdict: BLOCK

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

RATIO_404BURSTREFERER
01

Geolocation & Classification

IP Address
139.28.218.146
Type
Residential
Country
🇨🇦 Canada
City
Montreal
ISP
M247 Europe SRL
Organization
M247 LTD
Autonomous System
AS9009 M247 Europe SRL
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 60
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-11 11:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst: 5 req / 2s (+35), Foreign referer seen (+10)
2026-05-11 11:00:06
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

M247 Europe SRL
AS9009 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 139.28.218.146 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

🔎 Path Enumeration Protection

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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

139.28.218.146 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 139.28.218.146 to malicious activity originating from Montreal, Canada, operating on the network of M247 Europe SRL. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 111 flagged addresses, Canada represents a significant presence in our threat database. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

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

158.173.36.160 (305)45.91.20.90 (295)146.70.141.248 (280)66.225.209.6 (275)158.173.36.245 (270)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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: