ABUSE.MOM
THREAT REPORT

IP Threat Report
149.56.150.67

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:05:12
First seen: 2026-04-29 19:00:04
Last seen: 2026-04-29 19:00:04
210

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
149.56.150.67
Type
Hosting
Country
🇨🇦 Canada
City
Montreal
ISP
OVH SAS
Organization
Dataprovider B.V.
Autonomous System
AS16276 OVH SAS
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 3Medium-risk: admin panels, config files+30
Burst: 25 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 32 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 210
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-04-29 19:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 6 (+100), Danger medium hits: 3 (+30), Burst: 25 req / 2s (+35)
2026-04-29 19:00:04
Last malicious request observed
Total score reached: 210/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

OVH SAS
AS16276 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 149.56.150.67 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 149.56.150.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 149.56.150.67.

07

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

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

10

Threat Analysis

149.56.150.67 has been assigned a threat score of 210/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

Threat intelligence analysis has linked 149.56.150.67 to malicious activity originating from Montreal, Canada, operating on the network of OVH SAS. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 51 malicious IPs originating from Canada, positioning it as a notable contributor to global threat activity. At 210/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

151.243.236.245 (275)149.56.150.60 (210)149.56.150.69 (210)54.39.104.60 (205)15.235.83.135 (185)View all →

🏢 Same network: AS16276

51.38.99.224 (280)151.243.236.245 (275)54.37.156.148 (273)146.59.235.113 (263)51.83.98.78 (255)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: