ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.47.153

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 18:43:16
First seen: 2026-06-22 07:20:45
Last seen: 2026-06-27 23:57:20
255

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
135.136.47.153
Type
Unknown
Country
🇶🇦 QA
City
Doha
ISP
M247 Europe SRL
Organization
M247 Europe SRL
Autonomous System
Unknown
Hit Count
196
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Σ = 0
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-06-22 07:20:45
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-27 23:57:20
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 135.136.47.153 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
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ Defensive Recommendations

Block 135.136.47.153 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

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
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

135.136.47.153 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.

📊 Threat Analysis

135.136.47.153 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. Our sensors captured 196 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~39.2 requests per day. Our records show 56 malicious IPs originating from QA, positioning it as a notable contributor to global threat activity. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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.174 (255)135.136.47.214 (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.

💡 DNS-Based Threat Detection

Monitoring DNS queries reveals malicious activity including command-and-control communication, data exfiltration through DNS tunneling, and connections to known malicious domains. DNS is often the first indicator of compromise in network forensics.

🔍 Check Any IP Address

Share this report: