ABUSE.MOM
THREAT REPORT

IP Threat Report
149.56.160.252

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:04:50
First seen: 2026-07-08 09:19:04
Last seen: 2026-07-12 00:57:45
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

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

🤖 User-Agent Anomaly Defense

IP 149.56.160.252 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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
bl.blocklist.de

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

10

Threat Analysis

149.56.160.252 has been assigned a threat score of 105/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 149.56.160.252 has been traced to Montreal, Canada, operating on the network of OVH SAS. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 339 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~113 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 43 malicious IPs originating from Canada, positioning it as a notable contributor to global threat activity. 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.

💡 Credential Stuffing at Scale

Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.

🔍 Check Any IP Address

Share this report: