ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.0.6

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 05:47:17
First seen: 2026-06-29 04:15:32
Last seen: 2026-07-05 04:02:31
195

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
135.136.0.6
Type
Hosting
Country
🇩🇪 Germany
City
Frankfurt am Main
ISP
M247 Europe SRL
Organization
M247 Ltd Frankfurt
Autonomous System
AS9009 M247 Europe SRL
Hit Count
861
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 189/10sAbnormally fast request rate — automated scanning+35
Burst 189/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 18High-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-06-29 04:15:32
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), Danger strong hits: 18 (+100)
2026-07-05 04:02:31
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.6 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.6 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.0.6 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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

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

10

Threat Analysis

135.136.0.6 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

The address 135.136.0.6 originates from Frankfurt am Main, Germany, operating on the network of M247 Europe SRL. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 5-day observation window, we recorded 861 hostile requests from this IP — roughly 172.2 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Germany currently accounts for 119 blocked IPs in our database, making it a significant source of malicious traffic. 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 Germany

15.220.152.241 (320)35.246.204.221 (320)185.168.29.98 (313)77.81.65.244 (313)64.89.163.68 (308)View all →

🏢 Same network: AS9009

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

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

🔍 Check Any IP Address

Share this report: