ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.47.59

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 02:06:07
First seen: 2026-09-29 11:46:40
Last seen: 2026-10-04 00:53:06
200

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 19Medium-risk: admin panels, config files+60
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 200
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-09-29 11:46:40
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 19 (+60), Danger strong hits: 13 (+100), UA bot: Go-http-client (+40)
2026-10-04 00:53:06
Last malicious request observed
Total score reached: 200/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

M247 Europe SRL
AS9009 · 🇶🇦 QA

We have detected 208 malicious IPs from this autonomous system.

View all IPs from AS9009 →
06

Recommendations

Actions taken & recommended

  • IP 135.136.47.59 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

🤖 User-Agent Anomaly Defense

IP 135.136.47.59 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
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

User-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 135.136.47.59, geolocated to Doha, QA, operating on the network of M247 Europe SRL, as a source of suspicious network activity. During its 4-day observation window, we recorded 82 hostile requests from this IP — roughly 20.5 per day on average. 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. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. Our records show 101 malicious IPs originating from QA, positioning it as a significant contributor to global threat activity. At 200/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.173 (295)34.18.122.186 (288)34.18.235.87 (288)34.18.209.41 (288)34.18.110.181 (263)View all →

🏢 Same network: AS9009

45.91.20.151 (305)158.173.36.134 (305)135.136.42.150 (305)170.62.245.48 (305)135.136.41.102 (305)View all →
12

Security Intelligence

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 VPN Exit Node Reputation

VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.

🔍 Check Any IP Address

Share this report: