ABUSE.MOM
THREAT REPORT

IP Threat Report
149.56.160.176

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:04:50
First seen: 2026-07-14 23:26:33
Last seen: 2026-07-18 14:59:41
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 18/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 105
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-07-14 23:26:33
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 15/2s (+35), Burst 18/10s (+35), Foreign referer (+10)
2026-07-18 14:59:41
Last malicious request observed
Total score reached: 105/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.160.176 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.160.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

IP 149.56.160.176 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

Address UA spoofing from 149.56.160.176: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 149.56.160.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
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

149.56.160.176 has been assigned a threat score of 105/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 149.56.160.176 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 3 days, this IP generated 48 malicious requests, averaging approximately 16 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Canada currently accounts for 43 blocked IPs in our database, making it a notable source of malicious traffic. At 105/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

144.217.135.245 (125)149.56.160.153 (120)149.56.160.222 (120)149.56.150.26 (120)144.217.135.198 (120)View all →

🏢 Same network: AS16276

15.204.114.225 (263)213.32.71.245 (260)15.204.114.175 (253)15.204.114.172 (238)147.135.76.247 (223)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.

💡 Data Center IP Reputation

IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.

🔍 Check Any IP Address

Share this report: