ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.0.10

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:42:28
First seen: 2026-08-30 15:02:36
Last seen: 2026-09-06 00:34:16
195

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
135.136.0.10
Type
VPN
Country
🇩🇪 Germany
City
Spenge
ISP
M247 Europe SRL
Organization
M247 Ltd Frankfurt
Autonomous System
AS9009 M247 Europe SRL
Hit Count
283
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 189/10sAbnormally fast request rate — automated scanning+35
Burst 189/2sAbnormally fast request rate — automated scanning+35
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 41/2sAbnormally fast request rate — automated scanning+35
Burst 75/10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 400
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-30 15:02:36
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 189/10s (+35), Burst 189/2s (+35), Burst 25/2s (+35)
2026-09-06 00:34:16
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 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

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

07

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

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

10

Threat Analysis

135.136.0.10 has been assigned a threat score of 195/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

135.136.0.10 is registered in Spenge, Germany, 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 283 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~47.2 requests per day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 16 flagged addresses, Germany represents a notable presence in our threat database. With a threat score of 195/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇩🇪 Top threats from Germany

135.136.0.120 (220)135.136.0.107 (220)135.136.0.30 (195)135.136.0.6 (195)135.136.0.70 (195)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.

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

🔍 Check Any IP Address

Share this report: