ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.47.202

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 18:43:16
First seen: 2026-06-22 07:26:19
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: 195.

01

Geolocation & Classification

IP Address
135.136.47.202
Type
Unknown
Country
🇶🇦 QA
City
Doha
ISP
M247 Europe SRL
Organization
M247 Europe SRL
Autonomous System
Unknown
Hit Count
195
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:26:19
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.202 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

⚙️ General Security

Add 135.136.47.202 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

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

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

10

Threat Analysis

135.136.47.202 has been assigned a threat score of 255/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

Threat intelligence analysis has linked 135.136.47.202 to malicious activity originating from Doha, QA, operating on the network of M247 Europe SRL. The address has been under observation since its initial detection. Our sensors captured 195 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~39 requests per day. QA currently accounts for 56 blocked IPs in our database, making it a notable source of malicious traffic. At 255/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇶🇦 Top threats from QA

34.18.110.181 (263)34.18.114.23 (263)135.136.47.153 (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.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: