ABUSE.MOM
THREAT REPORT

IP Threat Report
149.56.160.206

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:04:50
First seen: 2026-07-12 04:34:12
Last seen: 2026-07-19 04:08:26
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 22/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-12 04:34:12
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 12/2s (+35), Burst 22/10s (+35), Foreign referer (+10)
2026-07-19 04:08:26
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.206 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

🌊 Flood / DDoS Mitigation

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

🤖 Bot Detection

Address UA spoofing from 149.56.160.206: 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
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

149.56.160.206 has been assigned a threat score of 105/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 149.56.160.206, located in Montreal, Canada, operating on the network of OVH SAS, has been classified as malicious by our automated threat scoring engine. Our sensors captured 524 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~87.3 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. With 43 flagged addresses, Canada represents a notable presence in our threat database. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.

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.

💡 Network Telescope and Darknet Monitoring

Network telescopes monitor large blocks of unused IP address space. Since no legitimate traffic should reach these addresses, all observed traffic represents scanning, backscatter from spoofed attacks, or misconfiguration — providing pure signal for threat analysis.

🔍 Check Any IP Address

Share this report: