ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.47.119

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:42:28
First seen: 2026-08-10 06:32:30
Last seen: 2026-08-16 00:30:49
195

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 25/10sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 195
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-08-10 06:32:30
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 25/10s (+35), Burst 7/2s (+35), Danger strong hits: 17 (+100)
2026-08-16 00:30:49
Last malicious request observed
Total score reached: 195/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.119 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.119 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 User-Agent Anomaly Defense

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

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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ 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

135.136.47.119 has been assigned a threat score of 195/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 FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 135.136.47.119 has been traced to Doha, QA, operating on the network of M247 Europe SRL. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 5 days, this IP generated 182 malicious requests, averaging approximately 36.4 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 195/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 QA

135.136.47.174 (255)135.136.47.214 (255)135.136.47.175 (255)135.136.47.100 (255)135.136.47.150 (255)View all →

🏢 Same network: AS9009

135.136.67.226 (270)135.136.47.174 (255)135.136.42.150 (255)135.136.42.24 (255)135.136.42.145 (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.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: