ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.47.150

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 18:43:16
First seen: 2026-07-17 14:25:25
Last seen: 2026-07-19 04:04:18
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
135.136.47.150
Type
Hosting
Country
🇶🇦 QA
City
Doha
ISP
M247 Europe SRL
Organization
M247 Ltd Qatar
Autonomous System
AS9009 M247 Europe SRL
Hit Count
34
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 30/10sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 969Medium-risk: admin panels, config files+60
Danger strong hits: 372High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 255
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-17 14:25:25
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 30/10s (+35), Burst 8/2s (+35), Danger medium hits: 969 (+60)
2026-07-19 04:04:18
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

M247 Europe SRL
AS9009 · 🇶🇦 QA
06

Recommendations

Actions taken & recommended

  • IP 135.136.47.150 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 135.136.47.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 135.136.47.150 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 135.136.47.150: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 135.136.47.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
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

135.136.47.150 is registered in Doha, QA, operating on the network of M247 Europe SRL. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 34 malicious requests, averaging approximately 34 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. QA currently accounts for 56 blocked IPs in our database, making it a notable source of malicious traffic. A score of 255/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 QA

34.18.110.181 (263)34.18.114.23 (263)135.136.47.202 (255)135.136.47.153 (255)135.136.47.174 (255)View all →

🏢 Same network: AS9009

135.136.47.174 (255)135.136.47.214 (255)135.136.47.175 (255)135.136.47.100 (255)135.136.47.22 (255)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.

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

🔍 Check Any IP Address

Share this report: